Triple
T30634974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan Hess |
E779813
|
entity |
| Predicate | hasReligionFamilyBackground |
P66371
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Morgan Hess, hasReligionFamilyBackground, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionFamilyBackground Context triple: [Morgan Hess, hasReligionFamilyBackground, Christianity]
-
A.
religiousFamilyBackground
chosen
Indicates that two entities are related through a shared or specified religious family upbringing or heritage.
-
B.
hasReligiousParent
Indicates that an entity has a parent who is associated with or practices a particular religion.
-
C.
religiousBackgroundOfCommunity
Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
-
D.
fatherReligion
Indicates the religious affiliation or belief system practiced or identified with by a person's father.
-
E.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: April 29, 2026, 8:28 p.m.