Triple
T28525492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont and Northern Railway |
E721892
|
entity |
| Predicate | passengerServiceEndedApprox |
P27833
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [Piedmont and Northern Railway, passengerServiceEndedApprox, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerServiceEndedApprox Context triple: [Piedmont and Northern Railway, passengerServiceEndedApprox, 1951]
-
A.
airportPassengerServiceEndedAt
Indicates that the provision of passenger-related services at an airport concluded at a specific time or event.
-
B.
ferryServiceEnded
Indicates that a previously operating ferry service between locations has been discontinued or terminated.
-
C.
railServiceEnded
chosen
Indicates that a previously operating rail service has been discontinued or terminated.
-
D.
timeOfJourneyEnd
Indicates the point in time at which a journey or trip concludes.
-
E.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 3:24 a.m.