Triple
T4012552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariamne II |
E90678
|
entity |
| Predicate | causeOfLossOfStatus |
P49654
|
FINISHED |
| Object | Herod’s discovery of plot involving her son |
—
|
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: Herod’s discovery of plot involving her son | Statement: [Mariamne II, causeOfLossOfStatus, Herod’s discovery of plot involving her son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLossOfStatus Context triple: [Mariamne II, causeOfLossOfStatus, Herod’s discovery of plot involving her son]
-
A.
reasonForLossOfSuccessionRights
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
-
B.
reasonForLossOfVote
Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
-
C.
demiseOfStatus
chosen
Indicates the ending or loss of a previously held status, role, or condition for an entity.
-
D.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
E.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.