Triple
T29382017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decision 2001/80/CFSP |
E745160
|
entity |
| Predicate | relatedToBody |
P37
|
FINISHED |
| Object | Political and Security Committee |
—
|
NE NERFINISHED |
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: Political and Security Committee | Statement: [Council Decision 2001/80/CFSP, relatedToBody, Political and Security Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToBody Context triple: [Council Decision 2001/80/CFSP, relatedToBody, Political and Security Committee]
-
A.
associatedBody
Indicates a relationship where one entity is linked or connected to another entity as its related or corresponding body.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
D.
relatedToPart
Indicates that one entity has a connection or association with a specific part or component of another entity.
-
E.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
- 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_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: April 28, 2026, 2:35 p.m.