Triple
T20308238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarai people |
E510161
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Jarai language |
—
|
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: Jarai language | Statement: [Jarai people, language, Jarai language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jarai language Context triple: [Jarai people, language, Jarai language]
-
A.
Jarai language
chosen
The Jarai language is an Austronesian language spoken by the Jarai people of Vietnam’s Central Highlands and neighboring Cambodia.
-
B.
Jahai language
The Jahai language is an indigenous Mon–Khmer language spoken by the Jahai people, a small hunter-gatherer community in the Malay Peninsula.
-
C.
Batui language
The Batui language is an Austronesian language spoken in Central Sulawesi, Indonesia, and is part of the Saluan–Banggai subgroup.
-
D.
Bariai language
The Bariai language is an Austronesian language spoken by the Bariai people of New Britain in Papua New Guinea.
-
E.
Tagin language
The Tagin language is a Tani (Tibeto-Burman) language spoken primarily by the Tagin people of Arunachal Pradesh in northeastern India.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677411cf08190ba7e98a4135b643a |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:18 a.m.