Triple
T9626119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nixon family |
E232468
|
entity |
| Predicate | hasReligiousBackground |
P48344
|
FINISHED |
| Object | Quakerism |
—
|
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: Quakerism | Statement: [Nixon family, hasReligiousBackground, Quakerism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousBackground Context triple: [Nixon family, hasReligiousBackground, Quakerism]
-
A.
hasDenominationalBackground
chosen
Indicates that an entity is associated with or originates from a particular religious denomination or tradition.
-
B.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
-
C.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
D.
religiousBackgroundOfCommunity
Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
-
E.
religiousFamilyBackground
Indicates that two entities are related through a shared or specified religious family upbringing or heritage.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afc9144819084b208c3d04174ba |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.