Triple
T19433358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenmesse |
E486169
|
entity |
| Predicate | successorActions |
P66307
|
FINISHED |
| Object | Seti II usurped his monuments |
—
|
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: Seti II usurped his monuments | Statement: [Amenmesse, successorActions, Seti II usurped his monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorActions Context triple: [Amenmesse, successorActions, Seti II usurped his monuments]
-
A.
successorAct
chosen
Indicates that one action or event directly follows and replaces another in a sequence or process.
-
B.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
C.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
-
D.
successorOperator
Indicates that one operator directly follows another in a defined sequence or ordering.
-
E.
successorPolicy
Indicates that one policy follows or replaces another policy in a sequence 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.