Triple
T9663515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU missions |
E233644
|
entity |
| Predicate | canIncludeTask |
P53912
|
FINISHED |
| Object | peacekeeping |
—
|
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: peacekeeping | Statement: [EU missions, canIncludeTask, peacekeeping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIncludeTask Context triple: [EU missions, canIncludeTask, peacekeeping]
-
A.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
B.
hasTaskType
Indicates that an entity is associated with or classified under a specific type or category of task.
-
C.
canBeAssignedTo
Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
-
D.
hasTaskGroup
Indicates that an entity is associated with, or belongs to, a specific task group that organizes or groups related tasks.
-
E.
mayIncludeFeature
chosen
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0cde048190b5a8e1548825d4d9 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.