Triple
T32921773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emma Smith |
E842161
|
entity |
| Predicate | marriedToReligiousFounder |
P113119
|
FINISHED |
| Object | Joseph Smith |
—
|
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: Joseph Smith | Statement: [Emma Smith, marriedToReligiousFounder, Joseph Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToReligiousFounder Context triple: [Emma Smith, marriedToReligiousFounder, Joseph Smith]
-
A.
spouseOfReligiousMovement
Indicates a marital relationship where one spouse is associated with, belongs to, or is significantly involved in a particular religious movement.
-
B.
hasReligiousFounderAssociated
Indicates that an entity is associated with a specific religious founder, typically through origin, dedication, or foundational influence.
-
C.
spouseOfFounderOf
Indicates that one entity is the spouse of another entity who is the founder of a specified organization or entity.
-
D.
founderOfReligionAssociated
Indicates that a person is the founder of a religion with which another entity is associated.
-
E.
spouseOfFounder
chosen
Indicates that one entity is the spouse (married partner) of the founder of 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:19 a.m.