Triple
T33409387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedumose I |
E855532
|
entity |
| Predicate | reignPositionInDynasty |
P170010
|
FINISHED |
| Object | late Thirteenth Dynasty ruler |
—
|
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: late Thirteenth Dynasty ruler | Statement: [Dedumose I, reignPositionInDynasty, late Thirteenth Dynasty ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignPositionInDynasty Context triple: [Dedumose I, reignPositionInDynasty, late Thirteenth Dynasty ruler]
-
A.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
B.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
-
C.
kingNumberWithinDynasty
chosen
Indicates the ordinal position of a king within a specific dynasty, expressing which numbered ruler he is in that dynastic sequence.
-
D.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
E.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
- 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_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:36 a.m.