Triple
T16885594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maraetai Power Station |
E421530
|
entity |
| Predicate | MaraetaiIICommissioned |
P6782
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Maraetai Power Station, MaraetaiIICommissioned, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MaraetaiIICommissioned Context triple: [Maraetai Power Station, MaraetaiIICommissioned, 1970]
-
A.
commissionedAt
chosen
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
B.
commissionedAfter
Indicates that one entity was formally authorized, ordered, or initiated at a later time than another entity.
-
C.
commissionedFor
Indicates that something was formally requested or created to serve a specific purpose, project, or recipient.
-
D.
commissioningUpon
Indicates that one entity formally authorizes, initiates, or assigns another entity to begin a specific role, task, or project.
-
E.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc126e881909dae8133ad34acc9 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.