Triple
T38281939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of the Islamic Emirate of Afghanistan |
E1022101
|
entity |
| Predicate | tookControlOfCapitalOn |
P190603
|
FINISHED |
| Object | 2021-08-15 |
—
|
LITERAL 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: 2021-08-15 | Statement: [Government of the Islamic Emirate of Afghanistan, tookControlOfCapitalOn, 2021-08-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookControlOfCapitalOn Context triple: [Government of the Islamic Emirate of Afghanistan, tookControlOfCapitalOn, 2021-08-15]
-
A.
seizesPowerBy
Indicates taking control or authority from others through forceful, coercive, or otherwise illegitimate means.
-
B.
tookControlOfGazaIn
Indicates that a specified actor assumed governing or military authority over Gaza in a particular year or time period.
-
C.
resultedInControlOfHouseBy
Indicates that one event, action, or circumstance caused or led to a particular party gaining control of a house.
-
D.
tookPowerInSaigon
Indicates that an entity assumed or seized political control or authority in Saigon.
-
E.
announcedAsNewCapitalOn
Indicates that a location was officially declared or designated as a new capital on a specific date.
- F. None of above. chosen
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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.