Triple
T36337866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Congress Party (Sudan) |
E894835
|
entity |
| Predicate | dateOfComingToPower |
P8145
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [National Congress Party (Sudan), dateOfComingToPower, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfComingToPower Context triple: [National Congress Party (Sudan), dateOfComingToPower, 1989]
-
A.
cameToPowerIn
chosen
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
B.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
C.
tookOfficeDuring
Indicates that one entity assumed or held an official position within the time period defined by another entity or event.
-
D.
governingSince
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
E.
dateOfTransferOfPower
Indicates the specific date on which governing authority or control is formally transferred from one party to another.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:09 p.m.