Triple
T35084125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lavinia railway station |
E1012530
|
entity |
| Predicate | distanceFromColomboFort |
P18161
|
FINISHED |
| Object | approximately 10 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: approximately 10 km | Statement: [Mount Lavinia railway station, distanceFromColomboFort, approximately 10 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromColomboFort Context triple: [Mount Lavinia railway station, distanceFromColomboFort, approximately 10 km]
-
A.
distanceToColombo
chosen
Indicates the measured or calculated spatial distance between a given entity’s location and the city of Colombo.
-
B.
distanceFromGalle_km
Indicates the physical distance, measured in kilometers, between an entity and the location Galle.
-
C.
distanceToBatticaloa_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Batticaloa.
-
D.
distanceToNegombo
Indicates the spatial distance between a given entity’s location and the location of Negombo.
-
E.
directionFromColombo
Indicates the cardinal or relative compass direction of an entity’s location measured from Colombo.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.