Triple
T9726815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothair II |
E235633
|
entity |
| Predicate | aimOfAnnulment |
P90683
|
FINISHED |
| Object | to secure a legitimate heir with Waldrada |
—
|
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: to secure a legitimate heir with Waldrada | Statement: [Lothair II, aimOfAnnulment, to secure a legitimate heir with Waldrada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfAnnulment Context triple: [Lothair II, aimOfAnnulment, to secure a legitimate heir with Waldrada]
-
A.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
B.
annulledBy
Indicates that an action, decision, or agreement has been officially invalidated or rendered void by a specified authority or agent.
-
C.
aimOfCondemnation
Indicates that an act of condemnation is directed toward a particular target or objective.
-
D.
denialObjective
Indicates that an agent’s goal is to prevent or obstruct another agent from obtaining, accessing, or achieving a particular resource, action, or outcome.
-
E.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e798c348190885b79d7dffc9d8d |
completed | April 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:21 p.m.