Triple
T30924299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence of South Sudan |
E787814
|
entity |
| Predicate | triggeredBorderIssuesWith |
P16224
|
FINISHED |
| Object | 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: Sudan | Statement: [Independence of South Sudan, triggeredBorderIssuesWith, Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredBorderIssuesWith Context triple: [Independence of South Sudan, triggeredBorderIssuesWith, Sudan]
-
A.
borderIssue
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
-
B.
borderConcern
chosen
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
C.
hasBorderConflictWith
Indicates a relationship where two entities share a disputed boundary or are involved in an ongoing or historical conflict over their common border.
-
D.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
E.
responsibleForBorder
Indicates that an entity has authority or duty to manage, control, or oversee a specific border or boundary.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b82df881909350359a39daa9ff |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.