Triple
T24420144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Jackson |
E615701
|
entity |
| Predicate | religiousOrSpiritualActivity |
P21643
|
FINISHED |
| Object | spiritualism |
—
|
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: spiritualism | Statement: [David Jackson, religiousOrSpiritualActivity, spiritualism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrSpiritualActivity Context triple: [David Jackson, religiousOrSpiritualActivity, spiritualism]
-
A.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
B.
practicesReligion
Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
-
C.
religiousMood
Indicates a prevailing emotional or spiritual atmosphere associated with religious experience, practice, or devotion between entities.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a227d08190bd4e3e4832c5a205 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.