Triple
T37985850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myall Creek massacre |
E947684
|
entity |
| Predicate | languageGroupAffected |
P134083
|
FINISHED |
| Object | Gamilaraay peoples |
E271593
|
NE 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: Gamilaraay peoples | Statement: [Myall Creek massacre, languageGroupAffected, Gamilaraay peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageGroupAffected Context triple: [Myall Creek massacre, languageGroupAffected, Gamilaraay peoples]
-
A.
languageAffected
Indicates that one entity has an impact on, modifies, or influences the characteristics, usage, or status of a language.
-
B.
languageGroupName
Indicates the name assigned to a particular language group or linguistic classification.
-
C.
languageGroupAttribution
chosen
Indicates that an entity is associated with, classified under, or attributed to a particular language group.
-
D.
languageGroupType
Indicates the classification relationship that specifies what type or category a particular language group belongs to.
-
E.
languageFamilyConcerned
Indicates that something is related to, involves, or pertains to a particular language family.
- F. None of above.
Provenance (4 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7ab1945f3881909d133c3ff89e19fb |
completed | Aug. 11, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: May 3, 2026, 4:20 p.m.