Triple
T30953521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilbury Ferry |
E788609
|
entity |
| Predicate | nearbyRailConnection |
P170255
|
FINISHED |
| Object | Tilbury Town railway station |
—
|
NE NERFINISHED |
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: Tilbury Town railway station | Statement: [Tilbury Ferry, nearbyRailConnection, Tilbury Town railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyRailConnection Context triple: [Tilbury Ferry, nearbyRailConnection, Tilbury Town railway station]
-
A.
railConnectionNearby
chosen
Indicates that there is a railway connection located close to the referenced entity or location.
-
B.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity to another entity.
-
C.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
D.
nearbyMajorStation
Indicates that one location is situated close to a major transportation station (such as a main train, bus, or metro hub).
-
E.
nearestRailwayLine
Indicates that one railway line is the closest in distance to a given location or feature compared to all other railway lines.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 8:53 p.m.