Triple
T35185327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traditional Owners of Kakadu |
E1015968
|
entity |
| Predicate | includeLanguageGroup |
P3349
|
FINISHED |
| Object | Gundjeihmi |
E2128228
|
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: Gundjeihmi | Statement: [Traditional Owners of Kakadu, includeLanguageGroup, Gundjeihmi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeLanguageGroup Context triple: [Traditional Owners of Kakadu, includeLanguageGroup, Gundjeihmi]
-
A.
hasLanguageGroup
chosen
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
B.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
C.
includesLanguageCluster
Indicates that one entity contains or encompasses a specific group or cluster of related languages as part of its composition or scope.
-
D.
languageGroupType
Indicates the classification relationship that specifies what type or category a particular language group belongs to.
-
E.
languageGroupAttribution
Indicates that an entity is associated with, classified under, or attributed to a particular language group.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb1e426c8190bcd533b6419a4e31 |
completed | June 21, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.