Triple
T30778492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Chartres |
E783743
|
entity |
| Predicate | heritageDesignationOfCathedral |
P82341
|
FINISHED |
| Object | UNESCO World Heritage Site |
—
|
NE NERFINISHED |
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: UNESCO World Heritage Site | Statement: [Diocese of Chartres, heritageDesignationOfCathedral, UNESCO World Heritage Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageDesignationOfCathedral Context triple: [Diocese of Chartres, heritageDesignationOfCathedral, UNESCO World Heritage Site]
-
A.
heritageStatusOfCathedral
chosen
Indicates the heritage designation or protection status assigned to a cathedral.
-
B.
cathedralUNESCOStatus
Indicates that a cathedral has a particular recognition or designation status from UNESCO.
-
C.
cathedralUNESCOInscriptionYear
Indicates the year in which a cathedral was officially inscribed on the UNESCO World Heritage List.
-
D.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
E.
cathedralDedication
Indicates the religious figure, event, or concept to which a cathedral is formally dedicated.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 8:41 p.m.