Triple
T18636693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsfield railway station |
E455567
|
entity |
| Predicate | directionFromLondonCharingCross |
P16893
|
FINISHED |
| Object | southeast |
—
|
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: southeast | Statement: [Chelsfield railway station, directionFromLondonCharingCross, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromLondonCharingCross Context triple: [Chelsfield railway station, directionFromLondonCharingCross, southeast]
-
A.
directionFromLondonKingsCross
Indicates the direction or bearing of a location when traveling from London King's Cross.
-
B.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
C.
directionFromCharingCross
chosen
Indicates the compass direction of one place or object as measured from Charing Cross.
-
D.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
-
E.
directionFromStAlbans
Indicates the compass direction or relative bearing of one place or object when measured starting from St Albans.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc90b508190849cecb462b52b62 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.