Triple
T38161636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abel Stearns |
E953030
|
entity |
| Predicate | religionByMarriage |
P137514
|
FINISHED |
| Object | Roman Catholicism |
—
|
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: Roman Catholicism | Statement: [Abel Stearns, religionByMarriage, Roman Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionByMarriage Context triple: [Abel Stearns, religionByMarriage, Roman Catholicism]
-
A.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
B.
spouseReligiousTradition
chosen
Indicates that there is a relationship specifying the religious tradition or affiliation of a person's spouse.
-
C.
regardsMarriageAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
-
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.
religiousCondition
Indicates a condition, requirement, or circumstance that is defined or constrained by religious beliefs, practices, or affiliations.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:21 p.m.