Triple
T36620572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakes State |
E904024
|
entity |
| Predicate | createdAsStateOf |
P156169
|
FINISHED |
| Object | Republic of South Sudan |
—
|
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: Republic of South Sudan | Statement: [Lakes State, createdAsStateOf, Republic of South Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsStateOf Context triple: [Lakes State, createdAsStateOf, Republic of South Sudan]
-
A.
createdAsState
Indicates that one entity brought another entity into existence specifically in the form or condition of a particular state.
-
B.
createdAsOutcomeOf
Indicates that one entity was brought into existence specifically as a result or consequence of another event, process, or action.
-
C.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
D.
becameStateOf
chosen
Indicates that an entity transitioned into and assumed the status, condition, or role defined by a particular state.
-
E.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.