Triple
T7787781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikka people |
E187290
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Sikka language |
E174813
|
NE 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: Sikka language | Statement: [Sikka people, language, Sikka language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sikka language Context triple: [Sikka people, language, Sikka language]
-
A.
Sika language
chosen
The Sika language is an Austronesian language spoken by the Sika people on the island of Flores in eastern Indonesia.
-
B.
Mikasuki language
The Mikasuki language is a Native American Muskogean language traditionally spoken by the Miccosukee and Seminole peoples of Florida.
-
C.
Kisukuma language
Kisukuma is a major Bantu language spoken primarily by the Sukuma people in northwestern Tanzania.
-
D.
Sakizaya language
The Sakizaya language is an indigenous Austronesian language spoken by the Sakizaya people of eastern Taiwan.
-
E.
Kawaiisu language
Kawaiisu language is an endangered Uto-Aztecan language traditionally spoken by the Kawaiisu people of southern California.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69caf61f77808190a5a1814fe1cb7ae1 |
completed | March 30, 2026, 10:15 p.m. |
Created at: March 30, 2026, 4:24 p.m.