Triple
T36996338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton-in-Arden railway station |
E915237
|
entity |
| Predicate | directionFromBirminghamNewStreet |
P196925
|
FINISHED |
| Object | 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: east | Statement: [Hampton-in-Arden railway station, directionFromBirminghamNewStreet, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromBirminghamNewStreet Context triple: [Hampton-in-Arden railway station, directionFromBirminghamNewStreet, east]
-
A.
directionFromBirmingham
Indicates the compass direction in which one entity is located relative to Birmingham.
-
B.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
C.
directionFromLiverpoolStreet
Indicates the directional relationship of one place or object as measured outward from Liverpool Street.
-
D.
directionFromNewbury
Indicates the cardinal or relative compass direction of one place or object as measured from Newbury.
-
E.
directionFromLondonFenchurchStreet
Indicates the compass direction or bearing of one place or object as measured from London Fenchurch Street.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:14 p.m.