Triple
T29933902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Río Churún |
E760302
|
entity |
| Predicate | UNESCOWorldHeritageStatusOfArea |
P63304
|
FINISHED |
| Object | World Heritage Site |
—
|
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: World Heritage Site | Statement: [Río Churún, UNESCOWorldHeritageStatusOfArea, World Heritage Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOWorldHeritageStatusOfArea Context triple: [Río Churún, UNESCOWorldHeritageStatusOfArea, World Heritage Site]
-
A.
UNESCOWorldHeritageAreaHa
Indicates that an area is designated as a UNESCO World Heritage site and specifies its size in hectares.
-
B.
UNESCODesignationArea
Indicates that a specified geographic area has been formally designated or recognized by UNESCO under one of its official programs or lists.
-
C.
UNESCOListStatus
chosen
Indicates that an entity has a specific recognition or classification status in relation to an official UNESCO list.
-
D.
UNESCOCoreZoneArea
Indicates the area encompassed by the core (legally protected) zone of a UNESCO-designated site.
-
E.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 6:18 p.m.