Triple
T212392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | List of World Heritage in Danger |
E4745
|
entity |
| Predicate | updateEvent |
P1664
|
FINISHED |
| Object | sessions of the World Heritage Committee |
—
|
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: sessions of the World Heritage Committee | Statement: [List of World Heritage in Danger, updateEvent, sessions of the World Heritage Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateEvent Context triple: [List of World Heritage in Danger, updateEvent, sessions of the World Heritage Committee]
-
A.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
B.
event
chosen
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
updateProcess
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
D.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c313d108190a65d3e939f961bef |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.