Triple
T25774116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salvation Mountain |
E649097
|
entity |
| Predicate | founderReligiousBelief |
P56366
|
FINISHED |
| Object | evangelical Christian |
—
|
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: evangelical Christian | Statement: [Salvation Mountain, founderReligiousBelief, evangelical Christian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderReligiousBelief Context triple: [Salvation Mountain, founderReligiousBelief, evangelical Christian]
-
A.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
B.
hasReligiousFounderAssociated
Indicates that an entity is associated with a specific religious founder, typically through origin, dedication, or foundational influence.
-
C.
religionOrBelief
chosen
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
D.
founderOfReligionAssociated
Indicates that a person is the founder of a religion with which another entity is associated.
-
E.
hasFounderOfReligion
Indicates that an entity is the person who founded or established a particular religion.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 22, 2026, 5:32 a.m.