Triple
T27421819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biete Meskel |
E693063
|
entity |
| Predicate | hasHeritageDesignationBy |
P921
|
FINISHED |
| Object | UNESCO |
—
|
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 | Statement: [Biete Meskel, hasHeritageDesignationBy, UNESCO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageDesignationBy Context triple: [Biete Meskel, hasHeritageDesignationBy, UNESCO]
-
A.
hasHeritageDesignationInArea
Indicates that an area has been assigned a specific heritage designation or protection status.
-
B.
hasHeritageDesignation
chosen
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
-
C.
hasHeritageDesignationRole
Indicates that an entity holds a specific role or status within a heritage designation or protection framework.
-
D.
hasHereditaryDesignation
Indicates that an entity possesses a title, status, or designation that is passed down through family lineage or inheritance.
-
E.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 12:36 p.m.