Triple
T2282960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermeticism |
E51320
|
entity |
| Predicate | viewsWorldAs |
P19063
|
FINISHED |
| Object | living cosmos |
—
|
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: living cosmos | Statement: [Hermeticism, viewsWorldAs, living cosmos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsWorldAs Context triple: [Hermeticism, viewsWorldAs, living cosmos]
-
A.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
B.
viewsClientAs
Indicates that one entity regards or treats another entity as a client within a service, business, or professional relationship.
-
C.
viewOnUniversals
Indicates a philosophical stance or theory an entity holds regarding the nature and existence of universals (e.g., whether they are real, conceptual, or merely linguistic).
-
D.
worldview
chosen
Indicates the overarching perspective or framework through which an entity interprets and understands the world and its experiences.
-
E.
viewsGraceAs
Indicates that one entity regards or perceives Grace in a particular way or role.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21d6d748190980128c1bc5b9621 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.