Triple
T28679582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctrine of Miracles |
E725970
|
entity |
| Predicate | hasWorldviewContext |
P77797
|
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: [The Doctrine of Miracles, hasWorldviewContext, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldviewContext Context triple: [The Doctrine of Miracles, hasWorldviewContext, Christianity]
-
A.
hasViewOnWorld
chosen
Indicates that an entity holds a particular perspective, opinion, or interpretation regarding the world or reality as a whole.
-
B.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
C.
hasParticularView
Indicates that one entity holds, expresses, or is characterized by a specific opinion, perspective, or standpoint regarding something.
-
D.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
E.
hasViewpointConcept
Indicates that something is associated with, characterized by, or defined through a particular viewpoint, perspective, or conceptual stance.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 5:08 a.m.