Triple
T31094492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desiderata |
E792487
|
entity |
| Predicate | reasonForEndOfMarriage |
P13503
|
FINISHED |
| Object | repudiation by Charlemagne |
—
|
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: repudiation by Charlemagne | Statement: [Desiderata, reasonForEndOfMarriage, repudiation by Charlemagne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEndOfMarriage Context triple: [Desiderata, reasonForEndOfMarriage, repudiation by Charlemagne]
-
A.
divorceReason
chosen
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
B.
marriageEndedBy
Indicates that a marriage relationship between two entities has been terminated due to the action or decision of a specified party or event.
-
C.
causeOfMarriage
Indicates that one entity is the reason or cause leading to the marriage of another entity or pair of entities.
-
D.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
E.
causeOfEndOfRelationship
Indicates that one entity is the reason or factor that led to the termination of a relationship between parties.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 9:03 p.m.