Triple
T25804449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Avery |
E649925
|
entity |
| Predicate | spiritualJourneyTheme |
P160688
|
FINISHED |
| Object | grief and reconciliation |
—
|
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: grief and reconciliation | Statement: [Tom Avery, spiritualJourneyTheme, grief and reconciliation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualJourneyTheme Context triple: [Tom Avery, spiritualJourneyTheme, grief and reconciliation]
-
A.
spiritualQuest
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
-
B.
mysticalTheme
Indicates that the subject is associated with or characterized by mystical, supernatural, or esoteric themes.
-
C.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
D.
spiritualMeans
Indicates that one entity serves as a spiritual method, medium, or pathway through which another entity attains or engages in a spiritual state, goal, or practice.
-
E.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
- F. None of above. chosen
Provenance (4 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60459a53c8190bbd90e80890eebcd |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f603b90c94819088d62cb9489e95ff |
completed | May 2, 2026, 2:01 p.m. |
Created at: April 22, 2026, 7:01 a.m.