Triple
T5246118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 2100 |
E118462
|
entity |
| Predicate | missionTypeEstablished |
P62372
|
FINISHED |
| Object | UN peacekeeping operation |
—
|
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: UN peacekeeping operation | Statement: [United Nations Security Council Resolution 2100, missionTypeEstablished, UN peacekeeping operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionTypeEstablished Context triple: [United Nations Security Council Resolution 2100, missionTypeEstablished, UN peacekeeping operation]
-
A.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
B.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
C.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
D.
notableMissionLaunched
Indicates that an entity (such as a space agency or organization) has launched a mission that is considered notable or significant.
-
E.
missionDesign
Indicates the relationship in which an entity plans, structures, and specifies the objectives, constraints, and procedures for carrying out a mission.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b515edc8190a9db198d4eb1c4f6 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79e9d794819097bb628c603d14af |
completed | March 20, 2026, 4:46 p.m. |
Created at: March 20, 2026, 1:49 p.m.