Triple
T7538406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Banda |
E178208
|
entity |
| Predicate | neighboringLanguages |
P16383
|
FINISHED |
| Object | Sango |
E274564
|
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: Sango | Statement: [Central Banda, neighboringLanguages, Sango]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sango Context triple: [Central Banda, neighboringLanguages, Sango]
-
A.
Sango
chosen
Sango is a Central African lingua franca and national language of the Central African Republic, originating as a Ngbandi-based trade language.
-
B.
Tanno
Tanno is a district or locality within the city of Kitami in Hokkaido, Japan.
-
C.
Ogunai
Ogunai is a small riverside settlement located along the Fly River in Papua New Guinea.
-
D.
Shingu
Shingu is a coastal city in Japan known for its historic Kumano Hongu Taisha shrine and its role as a gateway to the sacred Kumano Kodo pilgrimage routes.
-
E.
Nakanamanga
Nakanamanga is an Oceanic Austronesian language spoken primarily on Efate Island and nearby areas in Vanuatu.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8710400819088e430c8c550577e |
completed | March 27, 2026, 9:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84f108aec81909b0738b6273d5bd3 |
completed | March 28, 2026, 9:58 p.m. |
Created at: March 27, 2026, 3:48 p.m.