Triple
T34000461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Kordofan |
E871800
|
entity |
| Predicate | createdAsState |
P199377
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [South Kordofan, createdAsState, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsState Context triple: [South Kordofan, createdAsState, 1994]
-
A.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
B.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
C.
createdAsOutcomeOf
Indicates that one entity was brought into existence specifically as a result or consequence of another event, process, or action.
-
D.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
-
E.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
- F. None of above. chosen
Provenance (4 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
| PDg | Predicate description generation | batch_69ff32b6dd448190a7a6ebb76b99d4cc |
completed | May 9, 2026, 1:12 p.m. |
Created at: May 1, 2026, 1:50 a.m.