Triple
T30059602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton, West Virginia |
E763834
|
entity |
| Predicate | isServedByRailroad |
P782
|
FINISHED |
| Object | CSX Transportation |
—
|
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: CSX Transportation | Statement: [Grafton, West Virginia, isServedByRailroad, CSX Transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isServedByRailroad Context triple: [Grafton, West Virginia, isServedByRailroad, CSX Transportation]
-
A.
servedByRailroad
chosen
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
B.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
C.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
D.
servedRailroadsIn
Indicates that an individual or entity provided service or worked in an official capacity for one or more specified railroad companies.
-
E.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca2136881909b54de5f078579d9 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:57 p.m.