Triple
T26082549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Egypt and the Sudan |
E657883
|
entity |
| Predicate | deJureAuthorityOver |
P17826
|
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: [King of Egypt and the Sudan, deJureAuthorityOver, Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deJureAuthorityOver Context triple: [King of Egypt and the Sudan, deJureAuthorityOver, Sudan]
-
A.
legalAuthorityOver
chosen
Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
-
B.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
-
C.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
D.
hasSovereignAuthority
Indicates that one entity holds ultimate governing or ruling power over another entity or domain.
-
E.
canonicalJurisdictionOf
Indicates that one entity holds official legal or ecclesiastical authority over another entity or domain as its recognized jurisdiction.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606fcb3c48190930c7c6e532524d1 |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:39 p.m.