Triple
T36338559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudanese Islamist movement |
E894851
|
entity |
| Predicate | controlledParty |
P764
|
FINISHED |
| Object | National Islamic Front |
—
|
NE NERFINISHED |
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: National Islamic Front | Statement: [Sudanese Islamist movement, controlledParty, National Islamic Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledParty Context triple: [Sudanese Islamist movement, controlledParty, National Islamic Front]
-
A.
regulatedParty
Indicates that one entity is subject to rules, oversight, or control imposed by another regulating entity.
-
B.
collaboratingParty
Indicates that an entity is actively working together with another entity toward a shared goal, project, or activity.
-
C.
dominantParty
chosen
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
D.
otherSignificantParty
Indicates that an entity has another important associated party, such as a key counterpart, partner, or involved participant in a relationship or transaction.
-
E.
introducedParty
Indicates that one entity has brought another entity to the attention of, or formally presented them to, a third party or context.
- 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_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:09 p.m.