Triple
T283200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage Programme |
E5832
|
entity |
| Predicate | conventionAdoptedInYear |
P1362
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [UNESCO World Heritage Programme, conventionAdoptedInYear, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conventionAdoptedInYear Context triple: [UNESCO World Heritage Programme, conventionAdoptedInYear, 1972]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
conventionState
Indicates that an entity is in a particular formal status or phase within a convention or agreed procedural framework.
-
C.
standardizedInYear
Indicates the specific year in which something was formally standardized or adopted as a standard.
-
D.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
E.
officialAdoptionYear
chosen
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
- 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_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. |
Created at: Feb. 28, 2026, 3:02 a.m.