Triple
T21490985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenterden Town railway station |
E530233
|
entity |
| Predicate | hasLineDirection |
P130111
|
FINISHED |
| Object | towards Bodiam |
—
|
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: towards Bodiam | Statement: [Tenterden Town railway station, hasLineDirection, towards Bodiam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineDirection Context triple: [Tenterden Town railway station, hasLineDirection, towards Bodiam]
-
A.
hasLine9Direction
Indicates that an entity is associated with the specified travel direction of line 9 in a transit or route network.
-
B.
lineDirectionTo
Indicates the directional relationship from one line to another, such as whether they point in the same, opposite, or a specific relative direction.
-
C.
lineOrientation
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
-
D.
branchLineDirection
chosen
Indicates the directional orientation or flow of a branch line relative to a main line or reference point.
-
E.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea3aee648190ba845f0c7d8110dd |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.