Triple
T31980098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutberga of Arles |
E816551
|
entity |
| Predicate | causeOfDispute |
P107087
|
FINISHED |
| Object | Lothair II’s wish to marry his concubine 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: Lothair II’s wish to marry his concubine Waldrada | Statement: [Teutberga of Arles, causeOfDispute, Lothair II’s wish to marry his concubine Waldrada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDispute Context triple: [Teutberga of Arles, causeOfDispute, Lothair II’s wish to marry his concubine Waldrada]
-
A.
disputeIssue
chosen
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
B.
causeOfClaim
Indicates the underlying reason, event, or condition that gives rise to a particular claim.
-
C.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
D.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
E.
significantDispute
Indicates a serious, often prolonged disagreement or conflict exists between the involved entities.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 12:11 a.m.