Triple
T16630856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudanese conflict in South Kordofan and Blue Nile |
E404072
|
entity |
| Predicate | locatedInTimeAfter |
P6702
|
FINISHED |
| Object | South Sudan’s independence in 2011 |
—
|
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: South Sudan’s independence in 2011 | Statement: [Sudanese conflict in South Kordofan and Blue Nile, locatedInTimeAfter, South Sudan’s independence in 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimeAfter Context triple: [Sudanese conflict in South Kordofan and Blue Nile, locatedInTimeAfter, South Sudan’s independence in 2011]
-
A.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
B.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
C.
tookPlaceAfter
chosen
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
D.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
-
E.
chronologicallyAfter
Indicates that one event or state occurs later in time than 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e5d4448190bfb1b6157bbe5285 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.