Triple
T17378340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ongan |
E422499
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Jarawa 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: Jarawa language | Statement: [Ongan, hasPart, Jarawa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jarawa language Context triple: [Ongan, hasPart, Jarawa language]
-
A.
Jarawa language
chosen
The Jarawa language is an endangered Ongan language spoken by the indigenous Jarawa people of the Andaman Islands in India.
-
B.
Juruna language
The Juruna language is an indigenous Tupian language spoken by the Juruna (Yudjá) people of the Xingu region in Brazil.
-
C.
Warao language
The Warao language is an indigenous language isolate spoken by the Warao people of northeastern Venezuela and nearby regions, particularly in the Orinoco Delta.
-
D.
Tapirapé language
Tapirapé is an indigenous Tupian language spoken by the Tapirapé people of Brazil, known for its complex morphology and endangered status.
-
E.
Bororo language
The Bororo language is an indigenous Macro-Jê language of central Brazil, traditionally spoken by the Bororo people and known for its complex phonology and rich oral tradition.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6ea56c8190b56d966ccf2c91f7 |
completed | April 19, 2026, 2:14 a.m. |
Created at: April 10, 2026, 5:45 a.m.