Triple
T14672521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gẹ̀lẹ́dẹ́ masquerade |
E344547
|
entity |
| Predicate | UNESCOProclaimed |
P47605
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Gẹ̀lẹ́dẹ́ masquerade, UNESCOProclaimed, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOProclaimed Context triple: [Gẹ̀lẹ́dẹ́ masquerade, UNESCOProclaimed, 2001]
-
A.
UNESCORecognitionRelatedTo
Indicates a relationship where one entity’s recognition, designation, or status is formally granted or associated by UNESCO to another entity.
-
B.
unescoDesignation
chosen
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
C.
UNESCOHeritage
Indicates that a place, site, or cultural/natural asset has been officially inscribed on the UNESCO World Heritage List as having outstanding universal value.
-
D.
UNESCOSessionOfInscription
Indicates the specific UNESCO session during which an item was formally inscribed or added to a UNESCO list.
-
E.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb55064cc8190b9669d0b2da61825 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.