Triple
T3214003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinozism |
E67347
|
entity |
| Predicate | hasMetaphysicalView |
P4933
|
FINISHED |
| Object | substance monism |
—
|
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: substance monism | Statement: [Spinozism, hasMetaphysicalView, substance monism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetaphysicalView Context triple: [Spinozism, hasMetaphysicalView, substance monism]
-
A.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
B.
positionOnMetaphysics
chosen
Indicates a relationship where an entity’s stance, view, or theoretical commitment regarding metaphysical questions or issues is specified.
-
C.
hasPerspectiveOnParanormal
Indicates that one entity holds a particular view, belief, or attitude regarding paranormal phenomena in relation to another entity or topic.
-
D.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
E.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaabd01d48190be0dc610b9987a25 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.