Triple
T22341304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage monastery complexes |
E552279
|
entity |
| Predicate | mayHaveCriterion |
P50251
|
FINISHED |
| Object | UNESCO cultural criterion (i) |
—
|
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: UNESCO cultural criterion (i) | Statement: [UNESCO World Heritage monastery complexes, mayHaveCriterion, UNESCO cultural criterion (i)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveCriterion Context triple: [UNESCO World Heritage monastery complexes, mayHaveCriterion, UNESCO cultural criterion (i)]
-
A.
mayHaveRestriction
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
B.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
C.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
hasQualityCriterion
chosen
Indicates that something is associated with a specific standard or criterion used to judge its quality.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15794fae48190a2b79e9ae4b57bb1 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.