Triple
T6325390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mullah Mohammad Omar |
E141849
|
entity |
| Predicate | ruleEndedBy |
P54944
|
FINISHED |
| Object | 2001 U.S.-led invasion of Afghanistan |
—
|
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: 2001 U.S.-led invasion of Afghanistan | Statement: [Mullah Mohammad Omar, ruleEndedBy, 2001 U.S.-led invasion of Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleEndedBy Context triple: [Mullah Mohammad Omar, ruleEndedBy, 2001 U.S.-led invasion of Afghanistan]
-
A.
reasonForEndOfRule
chosen
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
B.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
C.
activityEndedBecauseOf
Indicates that an activity has come to an end specifically due to a particular cause, condition, or event.
-
D.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
E.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e701ec81908e5eaa0660d01a4b |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.