Triple
T31150462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyikang |
E794056
|
entity |
| Predicate | hasSuccessors |
P197449
|
FINISHED |
| Object | Shilluk kings |
—
|
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: Shilluk kings | Statement: [Nyikang, hasSuccessors, Shilluk kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessors Context triple: [Nyikang, hasSuccessors, Shilluk kings]
-
A.
hasCurrentSuccessor
Indicates that one entity is the immediate next or following entity in a current, ordered sequence or progression of another entity.
-
B.
hasMoreAggressiveSuccessor
Indicates that one entity is followed or replaced by another entity that exhibits a higher level of aggressiveness in behavior, strategy, or effect.
-
C.
hasOnlineSuccessor
Indicates that one entity is the direct online or digital successor of another, typically replacing or continuing its function in an online context.
-
D.
hasSuccessorUse
Indicates that one use or application of something is directly followed or replaced by another use in a sequence or progression.
-
E.
hasSuccessorUsers
Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69fe9208ed708190980fb5061b22ae49 |
completed | May 9, 2026, 1:46 a.m. |
Created at: April 29, 2026, 9:06 p.m.