Triple
T22933141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaili Ledo |
E569499
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Ledo Kaili |
—
|
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: Ledo Kaili | Statement: [Kaili Ledo, hasAlternativeName, Ledo Kaili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ledo Kaili Context triple: [Kaili Ledo, hasAlternativeName, Ledo Kaili]
-
A.
Ledo Kaili
chosen
Ledo Kaili is a major Austronesian language variety spoken by the Kaili people of Central Sulawesi, Indonesia.
-
B.
Kaili Ledo
Kaili Ledo is a major Austronesian language variety spoken by the Kaili people of Central Sulawesi, Indonesia.
-
C.
Ledo
Ledo is a town in Assam, India, historically known as the eastern terminus of the Indian Railways and the starting point of the World War II-era Stilwell Road.
-
D.
Ledo
Ledo is a dialect of the Kaili language spoken by communities in Central Sulawesi, Indonesia.
-
E.
Ado Kaili
Ado Kaili is a regional dialect of the Kaili language spoken by communities in Central Sulawesi, Indonesia.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181337ff881909d90cf3f5bae7516 |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:44 p.m.