Triple
T28399090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO declarations |
E719355
|
entity |
| Predicate | instrumentTypeOf |
P75978
|
FINISHED |
| Object | UNESCO normative instruments |
—
|
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: UNESCO normative instruments | Statement: [UNESCO declarations, instrumentTypeOf, UNESCO normative instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentTypeOf Context triple: [UNESCO declarations, instrumentTypeOf, UNESCO normative instruments]
-
A.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
B.
instrumentClassification
chosen
Indicates that one entity is classified as a particular type or category of instrument in relation to another entity.
-
C.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
D.
isInstrumentFor
Indicates that something is used as a tool or means to perform a particular action or achieve a specific outcome.
-
E.
instrumentForm
Indicates that one entity serves as the physical or structural form in which an instrument or tool is realized or embodied for 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 1:18 a.m.