Triple
T36180421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirissa railway station |
E1046692
|
entity |
| Predicate | hasApproximateDistanceToColombo |
P18161
|
FINISHED |
| Object | about 150 km |
—
|
LITERAL 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: about 150 km | Statement: [Mirissa railway station, hasApproximateDistanceToColombo, about 150 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDistanceToColombo Context triple: [Mirissa railway station, hasApproximateDistanceToColombo, about 150 km]
-
A.
distanceToColombo
chosen
Indicates the measured or calculated spatial distance between a given entity’s location and the city of Colombo.
-
B.
distanceToSriLanka
Indicates the spatial distance between a given entity’s location and the country of Sri Lanka.
-
C.
distanceFromGalle_km
Indicates the physical distance, measured in kilometers, between an entity and the location Galle.
-
D.
distanceToBatticaloa_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Batticaloa.
-
E.
distanceToNegombo
Indicates the spatial distance between a given entity’s location and the location of Negombo.
- F. None of above.
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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:08 p.m.