Triple
T17052352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominion Day |
E413729
|
entity |
| Predicate | statusAfterNameChange |
P46699
|
FINISHED |
| Object | superseded name |
—
|
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: superseded name | Statement: [Dominion Day, statusAfterNameChange, superseded name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterNameChange Context triple: [Dominion Day, statusAfterNameChange, superseded name]
-
A.
titleAfterNameChange
Indicates that the referenced title is the one held or used by an entity after a change to their name has occurred.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
legalStatusAfterRenaming
chosen
Indicates the legal status or classification that applies to an entity after it has undergone a renaming.
-
D.
changedSurnameTo
Indicates that an entity has adopted a new surname, replacing their previous one, with the new surname specified as the related entity.
-
E.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa3324881908d9e445ba1cfe109 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.