Triple
T283210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage Programme |
E5832
|
entity |
| Predicate | coversTypeOfSite |
P9088
|
FINISHED |
| Object | cultural 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: cultural site | Statement: [UNESCO World Heritage Programme, coversTypeOfSite, cultural site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversTypeOfSite Context triple: [UNESCO World Heritage Programme, coversTypeOfSite, cultural site]
-
A.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
B.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
C.
coversPolicyArea
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
D.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
E.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
- F. None of above. chosen
Provenance (4 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0c14b48190a5c936bab36180b3 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.