Triple
T34658815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santo Daime |
E890051
|
entity |
| Predicate | hasTheologyElement |
P181375
|
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: [Santo Daime, hasTheologyElement, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheologyElement Context triple: [Santo Daime, hasTheologyElement, Christianity]
-
A.
hasTheologicalElement
chosen
Indicates that something includes, expresses, or is characterized by a theological aspect, theme, or component.
-
B.
hasTheologicalAnalysisComponent
Indicates that something includes or is associated with a component involving theological analysis or examination.
-
C.
hasTheologicalMethod
Indicates a relationship where a subject employs, follows, or is characterized by a particular theological method or approach to doing theology.
-
D.
hasTheologicalSourceIn
Indicates that something derives its theological basis, authority, or origin from a specified source.
-
E.
hasTheologicalPurpose
Indicates that something is intended or designed to serve a religious or theological function or goal.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 2:04 a.m.