Triple
T25939280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Falls of Cheat |
E653646
|
entity |
| Predicate | hasRailAccessOperator |
P45263
|
FINISHED |
| Object | Durbin & Greenbrier Valley Railroad |
—
|
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: Durbin & Greenbrier Valley Railroad | Statement: [High Falls of Cheat, hasRailAccessOperator, Durbin & Greenbrier Valley Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailAccessOperator Context triple: [High Falls of Cheat, hasRailAccessOperator, Durbin & Greenbrier Valley Railroad]
-
A.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
B.
hasLocalRailOperator
chosen
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
-
C.
hasRailOperatorNamedAfter
Indicates that a rail operator is named after the specified entity.
-
D.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
E.
operatedOnRailroad
Indicates that an entity conducted operations or provided services on a railroad system.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 8:40 a.m.