Triple
T34348120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangam District |
E881491
|
entity |
| Predicate | hasSeenConflictIn |
P175780
|
FINISHED |
| Object | War in Afghanistan (2001–2021) |
—
|
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: War in Afghanistan (2001–2021) | Statement: [Dangam District, hasSeenConflictIn, War in Afghanistan (2001–2021)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeenConflictIn Context triple: [Dangam District, hasSeenConflictIn, War in Afghanistan (2001–2021)]
-
A.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
B.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
C.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
D.
sawConflict
chosen
Indicates that one entity perceived or became aware of a conflict involving another entity or situation.
-
E.
hasConflictCause
Indicates that one entity is the cause or source of a conflict involving another entity.
- 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_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 1, 2026, 1:58 a.m.