Triple
T27967068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plympton, Devon, England |
E704753
|
entity |
| Predicate | distanceToPlymouthCityCentre |
P28450
|
FINISHED |
| Object | approximately 4 miles east |
—
|
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 4 miles east | Statement: [Plympton, Devon, England, distanceToPlymouthCityCentre, approximately 4 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPlymouthCityCentre Context triple: [Plympton, Devon, England, distanceToPlymouthCityCentre, approximately 4 miles east]
-
A.
distanceToPlymouth
chosen
Indicates the measured distance between a given location or object and the place named Plymouth.
-
B.
distanceToYorkCityCentre
Indicates the measured or specified distance between a given location and the centre of York city.
-
C.
distanceToChesterCityCentre
Indicates the measured or specified distance between a given location and the centre of Chester city.
-
D.
distanceFromPoole
Indicates the spatial distance between a given entity and the location Poole.
-
E.
distanceFromCambridgeCentre
Indicates the spatial distance between a given entity and the central point of Cambridge.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 27, 2026, 7:35 p.m.