Triple
T25179860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellingham railway station |
E630553
|
entity |
| Predicate | hasRailSymbol |
P158412
|
FINISHED |
| Object | National Rail double-arrow |
—
|
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: National Rail double-arrow | Statement: [Bellingham railway station, hasRailSymbol, National Rail double-arrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailSymbol Context triple: [Bellingham railway station, hasRailSymbol, National Rail double-arrow]
-
A.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
B.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
C.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
-
D.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
E.
hasRailLevel
Indicates that one entity possesses, is assigned, or is associated with a specific rail-related level or classification in relation to another entity.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc4c3308190b9cb0ff4cbdc08d5 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 12:35 p.m.