Triple
T36543715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Service Commissioner (New Zealand) |
E901086
|
entity |
| Predicate | dateTitleCameIntoEffect |
P94738
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Public Service Commissioner (New Zealand), dateTitleCameIntoEffect, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateTitleCameIntoEffect Context triple: [Public Service Commissioner (New Zealand), dateTitleCameIntoEffect, 2020]
-
A.
titleDate
chosen
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
B.
firstUseAsTitleDate
Indicates the date on which something was first used as a title.
-
C.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
D.
endDateAsName
Indicates that an entity’s end date is represented or stored as a name-like string rather than as a standard date value.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.