Triple
T29163410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Sanders |
E739247
|
entity |
| Predicate | partnerInReligion |
P37062
|
FINISHED |
| Object | Maxine Sanders |
—
|
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: Maxine Sanders | Statement: [Alex Sanders, partnerInReligion, Maxine Sanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInReligion Context triple: [Alex Sanders, partnerInReligion, Maxine Sanders]
-
A.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
B.
sharesReligionWith
chosen
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
C.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
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.
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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 11:49 a.m.