Triple
T33257051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umon’hon’ti |
E851402
|
entity |
| Predicate | hasNameInOmahaLanguage |
P197993
|
FINISHED |
| Object | Umon’hon’ti |
—
|
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: Umon’hon’ti | Statement: [Umon’hon’ti, hasNameInOmahaLanguage, Umon’hon’ti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInOmahaLanguage Context triple: [Umon’hon’ti, hasNameInOmahaLanguage, Umon’hon’ti]
-
A.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
B.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
C.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
D.
hasNameInAnishinaabemowin
Indicates that an entity is known by a particular name expressed in the Anishinaabemowin language.
-
E.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
- F. None of above. chosen
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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:31 a.m.