Triple
T5576409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghari |
E146328
|
entity |
| Predicate | hasNeighbouringLanguage |
P16383
|
FINISHED |
| Object | Lengo |
E162602
|
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: Lengo | Statement: [Ghari, hasNeighbouringLanguage, Lengo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lengo Context triple: [Ghari, hasNeighbouringLanguage, Lengo]
-
A.
Langa
Langa is a surname and place name found in various cultures, notably in Southern Africa and parts of Europe.
-
B.
Lengo language
chosen
The Lengo language is an Oceanic language spoken on Guadalcanal in the Solomon Islands, known for its place within the Southeast Solomonic subgroup.
-
C.
Dili
Dili is the coastal capital and largest city of Timor-Leste, serving as its political, economic, and cultural center.
-
D.
Tangale
Tangale is a West Chadic language spoken primarily in Gombe State, northeastern Nigeria, by the Tangale people.
-
E.
Sanglechi language
The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020697fbc8190bd084d7896db3ab8 |
completed | March 22, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c02855acac8190bd00219aa9647e98 |
completed | March 22, 2026, 5:35 p.m. |
Created at: March 22, 2026, 3:37 p.m.