Triple
T19921646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arapaho |
E478808
|
entity |
| Predicate | selfDesignation |
P974
|
FINISHED |
| Object | Hinono’eino |
—
|
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: Hinono’eino | Statement: [Arapaho, selfDesignation, Hinono’eino]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hinono’eino Context triple: [Arapaho, selfDesignation, Hinono’eino]
-
A.
Hinono'eino
chosen
Hinono'eino is the autonym used by the Arapaho people to refer to themselves in their own language.
-
B.
Naishinnō
Naishinnō is a Japanese imperial title historically granted to princesses of the blood, denoting their status as high-ranking members of the Imperial Family.
-
C.
Hiniraya
Hiniraya is an alternate name for Kinaray-a, an Austronesian language spoken primarily in the Western Visayas region of the Philippines.
-
D.
Enneko
Enneko is a given name of Basque origin, often considered a variant of the name Eneko.
-
E.
Mehinako
Mehinako are an Indigenous people of the Upper Xingu region in Brazil, known for their distinct language, rich ritual traditions, and communal village life in the Amazon.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c6919c8190a96106532580b6b6 |
completed | April 20, 2026, 4:52 p.m. |
Created at: April 10, 2026, 1:53 p.m.