Triple
T36218121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umuwa |
E1047757
|
entity |
| Predicate | traditionalLanguageGroups |
P195717
|
FINISHED |
| Object | Pitjantjatjara |
—
|
NE NERFINISHED |
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: Pitjantjatjara | Statement: [Umuwa, traditionalLanguageGroups, Pitjantjatjara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLanguageGroups Context triple: [Umuwa, traditionalLanguageGroups, Pitjantjatjara]
-
A.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
B.
languageFamilyTraditional
Indicates that one entity belongs to, or is classified under, the traditional language family of the other entity.
-
C.
notableLanguageGroup
chosen
Indicates that there is a significant or noteworthy association between an entity and a particular language group.
-
D.
ethnicGroupLanguageOf
Indicates that a particular language is spoken by, associated with, or characteristic of a given ethnic group.
-
E.
languageTraditionally
Indicates that something is customarily or historically expressed, written, or communicated in a particular language.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:09 p.m.