Triple
T25774115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salvation Mountain |
E649097
|
entity |
| Predicate | primaryMessage |
P37146
|
FINISHED |
| Object | God is love and love everyone |
—
|
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: God is love and love everyone | Statement: [Salvation Mountain, primaryMessage, God is love and love everyone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMessage Context triple: [Salvation Mountain, primaryMessage, God is love and love everyone]
-
A.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
B.
primaryChannel
Indicates that one channel is designated as the main or most important channel among a set of available channels.
-
C.
centralMessage
chosen
Indicates the primary idea or core point that a communication, text, or message is intended to convey.
-
D.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 22, 2026, 5:32 a.m.