Triple
T16468637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solomonia Saburova |
E400001
|
entity |
| Predicate | causeOfAnnulment |
P28641
|
FINISHED |
| Object | failure to produce an heir |
—
|
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: failure to produce an heir | Statement: [Solomonia Saburova, causeOfAnnulment, failure to produce an heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAnnulment Context triple: [Solomonia Saburova, causeOfAnnulment, failure to produce an heir]
-
A.
reasonForAnnulment
chosen
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
B.
aimOfAnnulment
Indicates that an action or legal measure has the purpose or objective of nullifying, canceling, or invalidating something.
-
C.
annulledBy
Indicates that an action, decision, or agreement has been officially invalidated or rendered void by a specified authority or agent.
-
D.
causeOfMarriage
Indicates that one entity is the reason or cause leading to the marriage of another entity or pair of entities.
-
E.
annulmentDate
Indicates the date on which a previously established relationship, agreement, or status is formally declared null and void.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dce342081909cad56dc92de13a2 |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.