Triple
T29490395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy Mirando |
E748059
|
entity |
| Predicate | successorOrRival |
P195968
|
FINISHED |
| Object | Nancy Mirando |
—
|
NE NERFINISHED |
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: Nancy Mirando | Statement: [Lucy Mirando, successorOrRival, Nancy Mirando]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOrRival Context triple: [Lucy Mirando, successorOrRival, Nancy Mirando]
-
A.
successorRegimeOpposedByTitleHolder
Indicates that the regime succeeding a previous one is opposed or resisted by the holder of a particular title.
-
B.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
C.
dynasticRival
Indicates a relationship in which two entities belong to competing ruling lineages or houses that contest power or succession against each other.
-
D.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
E.
rivalClaimant
Indicates a relationship where two or more parties each assert competing rights or titles to the same position, asset, or claim, placing them in direct opposition.
- F. None of above. chosen
Provenance (4 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: April 28, 2026, 4:13 p.m.