Triple
T311897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage Convention |
E7625
|
entity |
| Predicate | criteriaType |
P4187
|
FINISHED |
| Object | cultural heritage criteria |
—
|
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: cultural heritage criteria | Statement: [UNESCO World Heritage Convention, criteriaType, cultural heritage criteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criteriaType Context triple: [UNESCO World Heritage Convention, criteriaType, cultural heritage criteria]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
C.
hasCriterionType
chosen
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
E.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.