Triple
T35835119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Central Railroad |
E1035910
|
entity |
| Predicate | operatedPassengerServiceUntil |
P6603
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Maine Central Railroad, operatedPassengerServiceUntil, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPassengerServiceUntil Context triple: [Maine Central Railroad, operatedPassengerServiceUntil, mid-20th century]
-
A.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
servesPassengersOn
Indicates that an entity provides transportation or service to passengers along a particular route, vehicle, or service context.
-
D.
openedAsPassengerService
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
E.
hasPassengerOperations
Indicates that an entity conducts or supports transportation services specifically for carrying passengers.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0189f3f0248190a1b018164d18e6f5 |
completed | May 11, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0187ee0920819097047bb55e1f9506 |
completed | May 11, 2026, 7:40 a.m. |
Created at: May 3, 2026, 4:06 p.m.