Triple
T26201810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic Republic of Afghanistan |
E655246
|
entity |
| Predicate | mainConflictOpponent |
P116426
|
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: [Islamic Republic of Afghanistan, mainConflictOpponent, Taliban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainConflictOpponent Context triple: [Islamic Republic of Afghanistan, mainConflictOpponent, Taliban]
-
A.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
B.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
C.
associatedOpponent
chosen
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
D.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
E.
intendedOpponents
Indicates that one entity is the target or adversary that another entity is meant or designed to oppose or confront.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 8:48 p.m.