Triple
T33409399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedumose I |
E855532
|
entity |
| Predicate | predecessorCertainty |
P194030
|
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, predecessorCertainty, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorCertainty Context triple: [Dedumose I, predecessorCertainty, uncertain]
-
A.
predecessorIsUncertain
chosen
Indicates that the identity or existence of the predecessor in a sequence or relationship is not known or cannot be determined with certainty.
-
B.
successorRelationCertainty
Indicates the degree of confidence or assurance that one entity is the successor of another in a given succession relationship.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorEstablished
Indicates that one entity was established before another, serving as its predecessor in origin or founding.
-
E.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 1:36 a.m.