Triple
T34348121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangam District |
E881491
|
entity |
| Predicate | hasInsurgentActivity |
P113370
|
FINISHED |
| Object | Taliban |
—
|
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: Taliban | Statement: [Dangam District, hasInsurgentActivity, Taliban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInsurgentActivity Context triple: [Dangam District, hasInsurgentActivity, Taliban]
-
A.
hasInsurgentGroupActivity
chosen
Indicates that insurgent groups are actively operating or conducting activities in relation to the referenced entity or context.
-
B.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
has activity
Indicates that one entity performs, exhibits, or is engaged in a particular action, behavior, or process associated with another entity.
-
D.
hasCenterOfUprising
Indicates that a location serves as the main focal point or hub where an uprising or rebellion is centered or originates.
-
E.
endedInsurgencyType
Indicates the specific manner or category of outcome by which an insurgency was brought to an end.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 1, 2026, 1:58 a.m.