Triple
T30308935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decision 2019/408/CFSP |
E770867
|
entity |
| Predicate | decisionNumber |
P172520
|
FINISHED |
| Object | 2019/408/CFSP |
—
|
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: 2019/408/CFSP | Statement: [Council Decision 2019/408/CFSP, decisionNumber, 2019/408/CFSP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionNumber Context triple: [Council Decision 2019/408/CFSP, decisionNumber, 2019/408/CFSP]
-
A.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
B.
decisionHolding
Indicates that an entity has made, issued, or is responsible for a particular formal decision or ruling.
-
C.
decisionPublication
Indicates that a decision has been formally published or made publicly available.
-
D.
decisionBody
Indicates that one entity serves as the authoritative body or group responsible for making a particular decision regarding another entity or matter.
-
E.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or entity.
- F. None of above. chosen
Provenance (4 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 29, 2026, 7:50 p.m.