Triple
T34079299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Pittsburgh Line |
E873988
|
entity |
| Predicate | hasRailfanLocation |
P192241
|
FINISHED |
| Object | Horseshoe Curve railfan overlook |
—
|
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: Horseshoe Curve railfan overlook | Statement: [Norfolk Southern Pittsburgh Line, hasRailfanLocation, Horseshoe Curve railfan overlook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailfanLocation Context triple: [Norfolk Southern Pittsburgh Line, hasRailfanLocation, Horseshoe Curve railfan overlook]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
liveLocation
Indicates that an entity’s current place of residence or primary location is at the specified place.
-
C.
hasReceiverLocation
Indicates that an entity serves as the destination or location where something is received by another party.
-
D.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
-
E.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:52 a.m.