Triple
T8836102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystery Play of Elche |
E210269
|
entity |
| Predicate | UNESCORecognitionDate |
P57323
|
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: [Mystery Play of Elche, UNESCORecognitionDate, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCORecognitionDate Context triple: [Mystery Play of Elche, UNESCORecognitionDate, 2001]
-
A.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
B.
inscribedOnUNESCOListInYear
chosen
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
C.
UNESCORecognitionRelatedTo
Indicates a relationship where one entity’s recognition, designation, or status is formally granted or associated by UNESCO to another entity.
-
D.
recognizedAsFirstUNESCOSiteIn
Indicates that an entity is acknowledged as the first UNESCO World Heritage Site within a specified place or jurisdiction.
-
E.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6069ad7881909e31010e73e26f91 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.