Triple
T33791678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qakare Ibi |
E865947
|
entity |
| Predicate | successorIs |
P78
|
FINISHED |
| Object | uncertain |
—
|
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: uncertain | Statement: [Qakare Ibi, successorIs, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorIs Context triple: [Qakare Ibi, successorIs, uncertain]
-
A.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
C.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
D.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
E.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:45 a.m.