Triple
T15012106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neostoicism |
E377862
|
entity |
| Predicate | viewsOnFate |
P13276
|
FINISHED |
| Object | Stoic fate reinterpreted as divine providence |
—
|
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: Stoic fate reinterpreted as divine providence | Statement: [Neostoicism, viewsOnFate, Stoic fate reinterpreted as divine providence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsOnFate Context triple: [Neostoicism, viewsOnFate, Stoic fate reinterpreted as divine providence]
-
A.
viewOnFate
chosen
Indicates a relationship where one entity holds a particular belief, attitude, or perspective about fate or predestination.
-
B.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
C.
knowledgeOfFate
Indicates that one entity is aware of or understands the destined or predetermined outcome concerning another entity or event.
-
D.
fateInBooks
Indicates that a character’s destiny, outcome, or predetermined path is described or revealed within written works or books.
-
E.
fateInLegend
Indicates the ultimate outcome or destiny attributed to an entity within a particular legend or mythic narrative.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7613cec8190ac25e3f68c5d0edf |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.