Triple
T32192695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Passage for Trumpet |
E822303
|
entity |
| Predicate | involvesNearDeathExperience |
P124566
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A Passage for Trumpet, involvesNearDeathExperience, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesNearDeathExperience Context triple: [A Passage for Trumpet, involvesNearDeathExperience, true]
-
A.
nearDeathExperience
chosen
Indicates that an entity has undergone a profound experience in close proximity to death or a life-threatening situation.
-
B.
experienceOfSouls
Indicates a relationship where certain experiences, states, or events are attributed specifically to souls as their subjects or bearers.
-
C.
visionaryExperiences
Indicates that an entity undergoes or has undergone profound, often transformative visionary or revelatory experiences.
-
D.
associatedAfterlife
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
E.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 1, 2026, 12:35 a.m.