Triple
T34665021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CityCenter |
E890227
|
entity |
| Predicate | brandChangeDate |
P48649
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [CityCenter, brandChangeDate, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandChangeDate Context triple: [CityCenter, brandChangeDate, 2018]
-
A.
brandingChangeDate
chosen
Indicates the date on which a change in branding (such as name, logo, or visual identity) took effect.
-
B.
brandRevivalDate
Indicates the date on which a previously inactive or discontinued brand was brought back into use or relaunched.
-
C.
platformChangeDate
Indicates the date on which a platform undergoes or records a change, such as an update, migration, or modification.
-
D.
serviceBranchChangeDate
Indicates the date on which an entity’s affiliation with a particular service branch was changed or updated.
-
E.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 2:04 a.m.