Triple
T20860948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camborne railway station |
E513614
|
entity |
| Predicate | lineDistanceFromPenzance |
P63708
|
FINISHED |
| Object | approximately 14 miles east of Penzance |
—
|
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 14 miles east of Penzance | Statement: [Camborne railway station, lineDistanceFromPenzance, approximately 14 miles east of Penzance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineDistanceFromPenzance Context triple: [Camborne railway station, lineDistanceFromPenzance, approximately 14 miles east of Penzance]
-
A.
distanceToPenzance
chosen
Indicates the spatial distance between a given entity’s location and the town of Penzance.
-
B.
distanceToTywyn
Indicates the spatial distance between a given entity and the location Tywyn.
-
C.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
D.
distanceToBodmin
Indicates the spatial distance between an entity and the location Bodmin.
-
E.
distanceToTruro
Indicates the measured spatial distance between a given location or entity and the place named Truro.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3aba3d0819093431f38f0095a71 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.