Triple
T33409400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedumose I |
E855532
|
entity |
| Predicate | successorCertainty |
P36359
|
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: [Dedumose I, successorCertainty, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCertainty Context triple: [Dedumose I, successorCertainty, uncertain]
-
A.
successorRelationCertainty
Indicates the degree of confidence or assurance that one entity is the successor of another in a given succession relationship.
-
B.
hasCertainty
chosen
Indicates that a statement, belief, or relationship is associated with a specific level or degree of confidence or surety.
-
C.
successorIsUncertain
Indicates that the identity of the next successor in a sequence, role, or position is not yet determined or is in doubt.
-
D.
positionOnCertainty
Indicates the degree or stance of confidence, doubt, or certainty an entity has regarding a particular proposition or situation.
-
E.
successorQualification
Indicates that one entity’s qualification or eligibility follows or replaces another’s in a sequence or succession.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 1, 2026, 1:36 a.m.