Triple
T7317935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mernda line |
E168461
|
entity |
| Predicate | reachedCurrentTerminus |
P70253
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Mernda line, reachedCurrentTerminus, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedCurrentTerminus Context triple: [Mernda line, reachedCurrentTerminus, 2018]
-
A.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
B.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
C.
endLocationOfJourney
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
-
D.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
E.
openedAsTerminus
chosen
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef178b3081908cd0c62466069741 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.