Triple
T7837555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISAF |
E181723
|
entity |
| Predicate | expandedMandate |
P58867
|
FINISHED |
| Object | countrywide operations beyond Kabul |
—
|
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: countrywide operations beyond Kabul | Statement: [ISAF, expandedMandate, countrywide operations beyond Kabul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedMandate Context triple: [ISAF, expandedMandate, countrywide operations beyond Kabul]
-
A.
mandateExpanded
chosen
Indicates that an entity’s scope of authority, responsibility, or mission has been broadened beyond its previous mandate.
-
B.
expandedJurisdictionOf
Indicates that an entity’s authority, control, or legal power has been extended to cover a broader scope, area, or set of subjects than it previously did.
-
C.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
D.
secondaryMandate
Indicates that an entity holds a subordinate or supporting mandate in addition to a primary mandate within a given context or system.
-
E.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c203b4819099c039c617628927 |
completed | March 31, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:46 p.m.