Triple
T18929240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khulo cable car |
E463055
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Khulo |
—
|
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: Khulo | Statement: [Khulo cable car, connects, Khulo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khulo Context triple: [Khulo cable car, connects, Khulo]
-
A.
Khulo
chosen
Khulo is a small mountainous town and municipality in southwestern Georgia’s Adjara region, known for its scenic landscapes and traditional highland culture.
-
B.
Thalochi
Thalochi is an alternative name for Thali, a term commonly associated with traditional South Asian platter-style meals featuring a variety of dishes served together.
-
C.
Mahlaing
Mahlaing is a town located in central Myanmar’s Mandalay Region.
-
D.
Raklungu
Raklungu is an indigenous local language spoken on Atauro Island, near Timor-Leste.
-
E.
Tlokwa
Tlokwa is a Sotho–Tswana-speaking ethnic group in Southern Africa, historically organized into chiefdoms and known for its distinct cultural and linguistic identity within the broader Sotho–Tswana peoples.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bea84081908fbe657fb4657c0b |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 10, 2026, 11:59 a.m.