Triple
T24231218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNSF Railway line |
E601736
|
entity |
| Predicate | railwayInfrastructureOperator |
P121930
|
FINISHED |
| Object | BNSF Railway |
—
|
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: BNSF Railway | Statement: [BNSF Railway line, railwayInfrastructureOperator, BNSF Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayInfrastructureOperator Context triple: [BNSF Railway line, railwayInfrastructureOperator, BNSF Railway]
-
A.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
-
B.
railwayOwner
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
C.
hasRailTransportOperator
chosen
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
D.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
E.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e3de908190917a5bf66d9df5c9 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:01 a.m.