Triple
T17270140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunts Cross |
E419233
|
entity |
| Predicate | locatedInDirectionFromLiverpoolCityCentre |
P126566
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Hunts Cross, locatedInDirectionFromLiverpoolCityCentre, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromLiverpoolCityCentre Context triple: [Hunts Cross, locatedInDirectionFromLiverpoolCityCentre, south]
-
A.
distanceFromLiverpoolCityCentre
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.
distanceToLiverpoolCentral
Indicates the spatial distance between a given location and Liverpool Central.
-
D.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
E.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
- F. None of above. chosen
Provenance (4 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4917ec819096356ad2ed24d51d |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.