Triple
T18688908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayors of Auckland |
E456937
|
entity |
| Predicate | changedSignificantlyOn |
P66871
|
FINISHED |
| Object | 2010-11-01 |
—
|
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: 2010-11-01 | Statement: [Mayors of Auckland, changedSignificantlyOn, 2010-11-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedSignificantlyOn Context triple: [Mayors of Auckland, changedSignificantlyOn, 2010-11-01]
-
A.
changedAfter
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
-
B.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
C.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
D.
changedOn
chosen
Indicates that an entity underwent a modification or update at a specific point in time.
-
E.
changedNumberOf
Indicates that the quantity of one entity has been altered by another entity 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2fc2cc8190a4726526a714a5eb |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.