Triple
T35413263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minister of Defense of the Islamic Emirate of Afghanistan |
E1023567
|
entity |
| Predicate | governingMovement |
P129817
|
FINISHED |
| Object | Taliban |
E26807
|
NE 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: Taliban | Statement: [Minister of Defense of the Islamic Emirate of Afghanistan, governingMovement, Taliban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingMovement Context triple: [Minister of Defense of the Islamic Emirate of Afghanistan, governingMovement, Taliban]
-
A.
dominantPoliticalMovement
chosen
Indicates that one political movement holds primary influence or control over the political landscape in a given context.
-
B.
notableMovementType
Indicates the type or category of significant movement or motion associated with an entity.
-
C.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
D.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
- F. None of above.
Provenance (4 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cd4a1f081909c0172acb5b26a75 |
completed | June 21, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:03 p.m.