Triple
T7317936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mernda line |
E168461
|
entity |
| Predicate | extensionOpenedToMernda |
P76268
|
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, extensionOpenedToMernda, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionOpenedToMernda Context triple: [Mernda line, extensionOpenedToMernda, 2018]
-
A.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
B.
extensionOpeningPeriod
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
C.
openedWith
Indicates that an entity is opened, initiated, or accessed using a specified tool, method, or instrument.
-
D.
opensOn
Indicates that an entity begins operating, becomes accessible, or starts being available at a specified time or on a specified date.
-
E.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or 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_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. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:02 p.m.