Triple
T31406999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhari District |
E801155
|
entity |
| Predicate | securityResponsibilityTransferredTo |
P144591
|
FINISHED |
| Object | Afghan National Security Forces (periods) |
—
|
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: Afghan National Security Forces (periods) | Statement: [Zhari District, securityResponsibilityTransferredTo, Afghan National Security Forces (periods)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityResponsibilityTransferredTo Context triple: [Zhari District, securityResponsibilityTransferredTo, Afghan National Security Forces (periods)]
-
A.
shiftedAuthorityTo
Indicates that decision-making power or control has been transferred from one entity to another.
-
B.
reallocatedResponsibilityFrom
Indicates that responsibility for something was transferred away from one party and assigned to another.
-
C.
ownershipTransferredTo
Indicates that the legal or formal ownership of an entity has been transferred from one party to another specified party.
-
D.
transferredAdministrationTo
chosen
Indicates that control or management authority over something was handed over from one party to another.
-
E.
securityResponsibilityModel
Indicates the framework or scheme that defines how security responsibilities are allocated and managed among involved parties.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 30, 2026, 8:33 p.m.