Triple
T32077310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunedin–Invercargill section |
E819191
|
entity |
| Predicate | openedByStages |
P26029
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Dunedin–Invercargill section, openedByStages, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedByStages Context triple: [Dunedin–Invercargill section, openedByStages, 19th century]
-
A.
openedInStages
chosen
Indicates that the opening or launch of something occurred in multiple distinct phases or stages rather than all at once.
-
B.
openedByEvent
Indicates that something is initiated, activated, or made accessible as a direct result of a specific event.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
openedAfter
Indicates that one entity was opened at a later time than another entity.
-
E.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 12:23 a.m.