Triple
T19792368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onehunga Line |
E475445
|
entity |
| Predicate | reopenedAsPassengerService |
P107520
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Onehunga Line, reopenedAsPassengerService, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsPassengerService Context triple: [Onehunga Line, reopenedAsPassengerService, 2010]
-
A.
openedAsPassengerService
chosen
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
B.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
C.
reopenedAsMBTAService
Indicates that a previously closed service or line was reopened specifically as part of the MBTA (Massachusetts Bay Transportation Authority) system.
-
D.
majorPassengerService
Indicates that a transportation facility or route provides primary or significant passenger service as one of its main functions.
-
E.
reopenedAsSBahn
Indicates that a previously closed or differently operated railway line or station was reopened specifically as part of an S-Bahn (urban rapid transit) system.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c37a3c819080f195d58adaaa7b |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.