Triple
T29493842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newton Bridge |
E748159
|
entity |
| Predicate | hasRailwayRole |
P107526
|
FINISHED |
| Object | intermediate station |
—
|
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: intermediate station | Statement: [Newton Bridge, hasRailwayRole, intermediate station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayRole Context triple: [Newton Bridge, hasRailwayRole, intermediate station]
-
A.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
B.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
railwayTrafficRole
chosen
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
-
E.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 4:16 p.m.