Triple
T32232542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poole railway station |
E823378
|
entity |
| Predicate | hasStationApproachFrom |
P4067
|
FINISHED |
| Object | Serpentine Road |
—
|
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: Serpentine Road | Statement: [Poole railway station, hasStationApproachFrom, Serpentine Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationApproachFrom Context triple: [Poole railway station, hasStationApproachFrom, Serpentine Road]
-
A.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
-
B.
hasApproachTrail
Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
-
C.
hasApproachRoad
chosen
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
D.
hasNearbyBridgeApproach
Indicates that one entity is located close to the approach section of a bridge associated with another entity.
-
E.
hasApproachTime
Indicates that an entity is associated with a specific time at which it approaches or comes near another entity or location.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 1, 2026, 12:39 a.m.