Triple
T7656684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gela |
E173401
|
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: [Gela, hasNeighbouringLanguage, Lengo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lengo Context triple: [Gela, hasNeighbouringLanguage, Lengo]
-
A.
Lengoʼ
Lengoʼ is an Oceanic language spoken by communities in the Solomon Islands, particularly on parts of Guadalcanal.
-
B.
Langa
Langa is a surname and place name found in various cultures, notably in Southern Africa and parts of Europe.
-
C.
Ikalanga
Ikalanga is a Bantu language spoken primarily by the Kalanga people in Botswana and southwestern Zimbabwe.
-
D.
Loenga
Loenga is a small residential and industrial neighborhood in Oslo, Norway, situated near the railway yards and the Oslofjord.
-
E.
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.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7018fcbb48190a479f2effd939a8e |
completed | March 27, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89b05846c8190b49540aeae43dd9a |
completed | March 29, 2026, 3:22 a.m. |
Created at: March 27, 2026, 3:59 p.m.