Triple
T21321600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jardwadjali people |
E525630
|
entity |
| Predicate | haveBeenAffectedBy |
P25489
|
FINISHED |
| Object | European colonisation of Victoria |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: European colonisation of Victoria | Statement: [Jardwadjali people, haveBeenAffectedBy, European colonisation of Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveBeenAffectedBy Context triple: [Jardwadjali people, haveBeenAffectedBy, European colonisation of Victoria]
-
A.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
B.
alsoAffects
Indicates that an action, condition, or change impacting one entity additionally impacts another entity as well.
-
C.
standAffected
Indicates that an entity is in a state or position of being impacted or influenced by another entity or event.
-
D.
canImpact
Indicates that one entity has the potential or ability to affect, influence, or cause a change in another entity.
-
E.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed1538c8190954da114e49dfa36 |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:39 p.m.