Triple
T3679448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huyton |
E78074
|
entity |
| Predicate | distanceToLiverpoolCityCentre |
P39185
|
FINISHED |
| Object | approximately 6 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 6 miles east | Statement: [Huyton, distanceToLiverpoolCityCentre, approximately 6 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLiverpoolCityCentre Context triple: [Huyton, distanceToLiverpoolCityCentre, approximately 6 miles east]
-
A.
distanceFromLiverpoolCityCentre
chosen
Indicates the spatial distance between a given location and the center of Liverpool city.
-
B.
distanceFromLiverpoolLimeStreet
Indicates the spatial distance between a given location and Liverpool Lime Street station.
-
C.
distanceToSunderland_km
Indicates the physical distance, measured in kilometers, between a given place and Sunderland.
-
D.
distanceToManchester
Indicates the measured or calculated distance between a given entity’s location and the city of Manchester.
-
E.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc49039308190b33082e2b58aa5cf |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.