Triple
T11340379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Ahmanet |
E268578
|
entity |
| Predicate | committedAction |
P18480
|
FINISHED |
| Object | murdered her father the Pharaoh |
—
|
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: murdered her father the Pharaoh | Statement: [Princess Ahmanet, committedAction, murdered her father the Pharaoh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: committedAction Context triple: [Princess Ahmanet, committedAction, murdered her father the Pharaoh]
-
A.
committed
chosen
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
B.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
C.
attemptedAction
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
D.
significantAction
Indicates that an action taken by an entity is of notable importance or consequence within a given context or process.
-
E.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea01c6c08190910a6ce8fb7e186d |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.