Triple
T11634926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pompeia Paulina |
E276491
|
entity |
| Predicate | loyaltyToSpouse |
P100117
|
FINISHED |
| Object | demonstrated by willingness to die with him |
—
|
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: demonstrated by willingness to die with him | Statement: [Pompeia Paulina, loyaltyToSpouse, demonstrated by willingness to die with him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyToSpouse Context triple: [Pompeia Paulina, loyaltyToSpouse, demonstrated by willingness to die with him]
-
A.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
B.
spouseCharacteristic
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
C.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
D.
spouseOrLover
Indicates a romantic partnership between two entities, whether formalized as a spouse or existing as a lover.
-
E.
governedThroughSpouse
Indicates that one entity exercised governing authority or political power indirectly through their spouse, who held the formal ruling position.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25c0b00819095898d2b2445ecfb |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.