Triple
T11311408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohi:yoʼ |
E267842
|
entity |
| Predicate | hasIndigenousNameStatus |
P96958
|
FINISHED |
| Object | traditional Seneca name |
—
|
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: traditional Seneca name | Statement: [Ohi:yoʼ, hasIndigenousNameStatus, traditional Seneca name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndigenousNameStatus Context triple: [Ohi:yoʼ, hasIndigenousNameStatus, traditional Seneca name]
-
A.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
-
B.
indigenousNameOf
chosen
Indicates that one entity is the name used for another entity in an indigenous or native language.
-
C.
hasIndigenousStatus
Indicates that an entity possesses a recognized indigenous status or is classified as indigenous according to a specific legal, cultural, or organizational framework.
-
D.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
E.
hasIndigenousLanguageRegion
Indicates that a region is associated with, or characterized by, the presence or use of one or more indigenous languages.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c1b7dc81908d8cc768c47390d3 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.