Triple
T19940583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumluova |
E479296
|
entity |
| Predicate | nearbySiteHasUNESCOStatus |
P16759
|
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: [Kumluova, nearbySiteHasUNESCOStatus, World Heritage Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySiteHasUNESCOStatus Context triple: [Kumluova, nearbySiteHasUNESCOStatus, World Heritage Site]
-
A.
nearbyWorldHeritageSite
chosen
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
B.
nearbyProtectedSite
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
-
C.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
D.
heritageSiteTypeNearby
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
E.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.