Triple
T26439142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh and West Virginia Railway |
E665036
|
entity |
| Predicate | primaryRouteFunction |
P196205
|
FINISHED |
| Object | bridge line |
—
|
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: bridge line | Statement: [Pittsburgh and West Virginia Railway, primaryRouteFunction, bridge line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRouteFunction Context triple: [Pittsburgh and West Virginia Railway, primaryRouteFunction, bridge line]
-
A.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
primaryRouteFrom
Indicates that one entity serves as the main or preferred route originating from another entity.
-
C.
primaryRoutes
Indicates the main or most important routes that connect or serve between specified locations or entities.
-
D.
primaryRouteOf
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
-
E.
primaryEntryRoutes
Indicates the main routes or pathways through which something first enters or is accessed.
- F. None of above. chosen
Provenance (4 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: April 26, 2026, 11:56 p.m.