Triple
T35157178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Therasia |
E1015154
|
entity |
| Predicate | roleInMarriage |
P203148
|
FINISHED |
| Object | spiritual partner of Paulinus of Nola |
—
|
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: spiritual partner of Paulinus of Nola | Statement: [Therasia, roleInMarriage, spiritual partner of Paulinus of Nola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMarriage Context triple: [Therasia, roleInMarriage, spiritual partner of Paulinus of Nola]
-
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.
roleInSpouseCareer
Indicates the nature or extent of a person’s involvement or influence in their spouse’s professional career.
-
D.
weddingRole
Indicates the specific role or function an entity has in the context of a wedding event.
-
E.
roleDuringSpouseTenure
Indicates that a person held a particular role or position specifically during the period when their spouse was in office or serving in a defined tenure.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_6a01289ecf7481908802642bb4399ac0 |
completed | May 11, 2026, 12:53 a.m. |
Created at: May 3, 2026, 4:02 p.m.