Triple
T23776899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Leader of the Islamic Emirate of Afghanistan |
E587699
|
entity |
| Predicate | office_created |
P53503
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Supreme Leader of the Islamic Emirate of Afghanistan, office_created, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: office_created Context triple: [Supreme Leader of the Islamic Emirate of Afghanistan, office_created, 1996]
-
A.
officeCreatedFor
Indicates that an office or position was established specifically to serve, represent, or support a particular entity.
-
B.
officeCreatedUnder
Indicates that an office was established or formed under the authority, jurisdiction, or organizational structure of a particular entity or governing body.
-
C.
officeCreatedOn
chosen
Indicates the date on which an office was formally established or created.
-
D.
officeCreatedAlongWith
Indicates that an office was established at the same time as another specified entity, event, or office.
-
E.
officeCreatedAsResultOf
Indicates that an office came into existence as a consequence of a specific preceding event, action, or process.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46d55588190ad9c7e3c729b6b17 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.