Triple
T35157166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Therasia |
E1015154
|
entity |
| Predicate | partnerInReligiousLifeWith |
P182900
|
FINISHED |
| Object | Paulinus of Nola |
—
|
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: Paulinus of Nola | Statement: [Therasia, partnerInReligiousLifeWith, Paulinus of Nola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInReligiousLifeWith Context triple: [Therasia, partnerInReligiousLifeWith, Paulinus of Nola]
-
A.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
B.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
C.
religiousAndSpiritualRole
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
-
D.
spouseReligiousRole
Indicates that one person’s role or position in a religious context is defined in relation to their spouse’s religious role.
-
E.
devotionalRelationship
Indicates a relationship in which one entity expresses deep religious or spiritual devotion, reverence, or worship toward another entity.
- 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_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:02 p.m.