Triple
T12971554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanimbar Islands |
E321408
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Selaru language |
E148731
|
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: Selaru language | Statement: [Tanimbar Islands, language, Selaru language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Selaru language Context triple: [Tanimbar Islands, language, Selaru language]
-
A.
Selaru language
chosen
The Selaru language is an Austronesian language spoken on Selaru Island in Indonesia’s Tanimbar Islands, known for its place within the Central Malayo-Polynesian subgroup.
-
B.
Saluan language
The Saluan language is an Austronesian language spoken by the Saluan people of central and eastern Sulawesi, Indonesia.
-
C.
Sura language
The Sura language is a Chadic language of the Afroasiatic family spoken by the Sura people in central Nigeria.
-
D.
Murle language
The Murle language is an Eastern Sudanic language spoken primarily by the Murle people of South Sudan.
-
E.
Suri language
The Suri language is a Surmic language spoken by the Suri (Surma) people of southwestern Ethiopia, known for its complex tone system and rich oral tradition.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e418d548190be1c73db76cb3aa8 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8ea91f08190b1daf6d05621acf9 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:36 p.m.