Triple
T22569775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhi |
E558047
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Na-khi |
—
|
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: Na-khi | Statement: [Nakhi, hasAlternativeName, Na-khi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Na-khi Context triple: [Nakhi, hasAlternativeName, Na-khi]
-
A.
Na-kara
Na-kara is an Indigenous Australian Aboriginal language traditionally spoken in the Maningrida region of the Northern Territory.
-
B.
Nako
Nako was a 10th-century Slavic prince of the Obotrite confederation known for his role in regional power struggles and interactions with the German Holy Roman Empire.
-
C.
Nako
Nako is a high-altitude Himalayan village in Himachal Pradesh, India, known for its scenic lake, ancient monasteries, and traditional Tibetan-influenced culture.
-
D.
Nokhchi
chosen
Nokhchi is the endonym used by the Chechen people to refer to themselves as an ethnic group indigenous to the North Caucasus region.
-
E.
Nikaho
Nikaho is a coastal city in northern Japan known for its scenic Sea of Japan shoreline and location in southwestern Akita Prefecture.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fad35448190b51a3dd639ca8568 |
completed | April 29, 2026, 1:32 a.m. |
Created at: April 16, 2026, 8:52 p.m.