Triple
T38483896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Interstate Railroad |
E917859
|
entity |
| Predicate | usesRailInfrastructureType |
P63327
|
FINISHED |
| Object | heavy rail |
—
|
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: heavy rail | Statement: [Iowa Interstate Railroad, usesRailInfrastructureType, heavy rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRailInfrastructureType Context triple: [Iowa Interstate Railroad, usesRailInfrastructureType, heavy rail]
-
A.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
B.
isRailInfrastructure
Indicates that something functions as or is classified as part of a railway-related physical infrastructure or system.
-
C.
hasRailwayInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
D.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
E.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:31 p.m.