Triple
T27014927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage Site |
E680498
|
entity |
| Predicate | naturalCriteriaRange |
P133442
|
FINISHED |
| Object | vii–x |
—
|
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: vii–x | Statement: [UNESCO World Heritage Site, naturalCriteriaRange, vii–x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalCriteriaRange Context triple: [UNESCO World Heritage Site, naturalCriteriaRange, vii–x]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
C.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
D.
rangeRestrictedTo
Indicates that the possible values or targets of a relation are constrained to lie within a specified set or type.
-
E.
hasRangeCategory
chosen
Indicates that a property or measurement falls within a specified category or interval of possible values.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:05 a.m.