Triple
T2368446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waitangi Day |
E46035
|
entity |
| Predicate | earlierNameChangeYear |
P25649
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [Waitangi Day, earlierNameChangeYear, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierNameChangeYear Context triple: [Waitangi Day, earlierNameChangeYear, 1973]
-
A.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
B.
previousNameUsedUntil
chosen
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
originalNameUsedInYears
Indicates that a particular original name was in use for an entity during a specified range of years.
-
D.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
E.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76bf75c8190b014c3dbfc46bba3 |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.