Triple
T7335299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbombela |
E169111
|
entity |
| Predicate | hasNameChangeYear |
P801
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Mbombela, hasNameChangeYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameChangeYear Context triple: [Mbombela, hasNameChangeYear, 2009]
-
A.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
B.
underwentNameChangeTo
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
C.
nameChangeDate
chosen
Indicates the date on which an entity’s name was officially changed.
-
D.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
E.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.