Triple
T38134659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siobhán O'Donnell |
E952315
|
entity |
| Predicate | marriageRole |
P124855
|
FINISHED |
| Object | dynastic alliance partner |
—
|
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: dynastic alliance partner | Statement: [Siobhán O'Donnell, marriageRole, dynastic alliance partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageRole Context triple: [Siobhán O'Donnell, marriageRole, dynastic alliance partner]
-
A.
afterMarriageRole
Indicates the role or status an entity assumes following a marriage event.
-
B.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
-
C.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
D.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
E.
hasMaritalFunction
chosen
Indicates that one entity serves a role or performs a function within the context of a marital relationship or institution.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:21 p.m.