Triple
T8680070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States-led coalition |
E206013
|
entity |
| Predicate | beganMajorOperationsIn |
P5415
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [United States-led coalition, beganMajorOperationsIn, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganMajorOperationsIn Context triple: [United States-led coalition, beganMajorOperationsIn, 2014]
-
A.
beganCivilOperations
Indicates that an entity initiated or commenced civil (non-military) administrative or operational activities in relation to another entity or context.
-
B.
hadMajorOperationsIn
Indicates that an entity has undergone significant or primary operations or activities in a specified location or context.
-
C.
trialOperationsBegan
Indicates that the operational phase of a trial has started.
-
D.
majorOperation
Indicates that one entity performs or undergoes a significant, large-scale, or primary operation or procedure involving another entity or context.
-
E.
startOfMajorCampaign
chosen
Indicates that the referenced event marks the beginning of a significant, large-scale campaign or operation.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.