Triple
T3580231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appendix III |
E75781
|
entity |
| Predicate | hasTypeOfInstrument |
P12711
|
FINISHED |
| Object | multilateral environmental agreement annex |
—
|
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: multilateral environmental agreement annex | Statement: [Appendix III, hasTypeOfInstrument, multilateral environmental agreement annex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfInstrument Context triple: [Appendix III, hasTypeOfInstrument, multilateral environmental agreement annex]
-
A.
typeOfInstrument
chosen
Indicates the specific kind or category of instrument associated with an entity.
-
B.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
E.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0ffecdc8190bf01c8ba90e3733e |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.