Triple
T29382034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decision 2001/80/CFSP |
E745160
|
entity |
| Predicate | linkedToInstrument |
P45000
|
FINISHED |
| Object | CFSP joint actions and operations |
—
|
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: CFSP joint actions and operations | Statement: [Council Decision 2001/80/CFSP, linkedToInstrument, CFSP joint actions and operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToInstrument Context triple: [Council Decision 2001/80/CFSP, linkedToInstrument, CFSP joint actions and operations]
-
A.
linkedInstrument
chosen
Indicates that one entity is associated with or connected to another as a related or corresponding instrument.
-
B.
relatedToInstrument
Indicates a general relationship where one entity is connected or associated with a musical instrument.
-
C.
relatesToInstrument
Indicates a relationship where one entity is associated with, involves, or makes use of a particular instrument or tool.
-
D.
belongsToInstrument
Indicates that something is a component, part, or attribute of a specific instrument.
-
E.
affectedInstrument
Indicates that an instrument or tool is impacted, altered, or influenced as a result of an action or event.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 28, 2026, 2:35 p.m.