Triple
T37235098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monaco |
E923550
|
entity |
| Predicate | rebrandingAnnouncedOn |
P48649
|
FINISHED |
| Object | 2018-07-06 |
—
|
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-07-06 | Statement: [Monaco, rebrandingAnnouncedOn, 2018-07-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandingAnnouncedOn Context triple: [Monaco, rebrandingAnnouncedOn, 2018-07-06]
-
A.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
B.
rebrandedYear
Indicates the year in which an entity changed its brand identity, such as its name, logo, or overall branding.
-
C.
brandingChangeDate
chosen
Indicates the date on which a change in branding (such as name, logo, or visual identity) took effect.
-
D.
rebrandPeriod
Indicates the time span during which an entity undergoes or is designated for a rebranding.
-
E.
brandRevivalDate
Indicates the date on which a previously inactive or discontinued brand was brought back into use or relaunched.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.