Triple
T35315332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Kordofan State |
E1019887
|
entity |
| Predicate | previouslyAbolishedIn |
P109071
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [West Kordofan State, previouslyAbolishedIn, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyAbolishedIn Context triple: [West Kordofan State, previouslyAbolishedIn, 2005]
-
A.
previouslyAbolished
chosen
Indicates that something was officially ended, discontinued, or annulled at some point in the past.
-
B.
wasAbolishedInContextOf
Indicates that something (such as a law, practice, institution, or position) was formally ended or eliminated specifically within, or as part of, a particular event, process, or broader situational context.
-
C.
wasAbolishedBy
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
-
D.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
E.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:03 p.m.