Triple
T14448721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darug language |
E358272
|
entity |
| Predicate | impactOfColonisation |
P6677
|
FINISHED |
| Object | language shift to English |
—
|
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: language shift to English | Statement: [Darug language, impactOfColonisation, language shift to English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOfColonisation Context triple: [Darug language, impactOfColonisation, language shift to English]
-
A.
impactOnColonies
Indicates the effect or influence that one factor, event, or condition has on colonies.
-
B.
colonialLegacy
chosen
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
C.
regionOfColonization
Indicates the geographic area or territory where a colonizing entity establishes and exercises colonial control.
-
D.
colonialPerception
Indicates how one entity views, interprets, or characterizes another through the lens of colonial power dynamics, assumptions, and hierarchies.
-
E.
colonialChange
Indicates a change in colonial status or control of a territory, such as gaining, losing, or altering colonial rule.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916139888190be219678e29a2a3a |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.