Triple
T29873354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Party of the Netherlands |
E758652
|
entity |
| Predicate | treatyShortName |
P9302
|
FINISHED |
| Object | UNESCO World Heritage Convention |
—
|
NE NERFINISHED |
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: UNESCO World Heritage Convention | Statement: [State Party of the Netherlands, treatyShortName, UNESCO World Heritage Convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyShortName Context triple: [State Party of the Netherlands, treatyShortName, UNESCO World Heritage Convention]
-
A.
treatyName
Indicates the formal name or title assigned to a specific treaty.
-
B.
treatyAlsoKnownAs
chosen
Indicates that a treaty is referred to by an alternative name or alias.
-
C.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
D.
treatyNameDerivedFrom
Indicates that the name of a treaty is derived from, or based on, another specified source such as a place, person, event, or document.
-
E.
treatyType
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 5:54 p.m.