Triple
T15666191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad Hoc Open-ended Working Group on Access and Benefit-sharing |
E377192
|
entity |
| Predicate | worksOnInstrumentType |
P12711
|
FINISHED |
| Object | international regime |
—
|
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: international regime | Statement: [Ad Hoc Open-ended Working Group on Access and Benefit-sharing, worksOnInstrumentType, international regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnInstrumentType Context triple: [Ad Hoc Open-ended Working Group on Access and Benefit-sharing, worksOnInstrumentType, international regime]
-
A.
typeOfInstrument
chosen
Indicates the specific kind or category of instrument associated with an entity.
-
B.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
C.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0f4df08190ad2c5d78e435d8eb |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.