Triple
T36092264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solve Coagula |
E1043952
|
entity |
| Predicate | hasConceptualInfluence |
P45664
|
FINISHED |
| Object | occult philosophy |
—
|
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: occult philosophy | Statement: [Solve Coagula, hasConceptualInfluence, occult philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConceptualInfluence Context triple: [Solve Coagula, hasConceptualInfluence, occult philosophy]
-
A.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
B.
hasEnduringInfluenceOn
Indicates that one entity exerts a lasting, long-term impact on another entity’s state, development, or behavior.
-
C.
hadInfluenceOn
chosen
Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
-
D.
hasHistoricalInfluenceFrom
Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy of another entity.
-
E.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.