Triple
T33833901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Death |
E867178
|
entity |
| Predicate | positionOnLife |
P59938
|
FINISHED |
| Object | life is predominantly painful |
—
|
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: life is predominantly painful | Statement: [On Death, positionOnLife, life is predominantly painful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLife Context triple: [On Death, positionOnLife, life is predominantly painful]
-
A.
positionOnHumanLife
chosen
Indicates a stance or viewpoint that an entity holds regarding the value, rights, or treatment of human life.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionOnDeath
Indicates the role, title, or position an entity held at the time of its death.
-
D.
positionOnTreeOfLife
Indicates the relative placement of an entity within the evolutionary hierarchy or branching structure of the tree of life.
-
E.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 1, 2026, 1:46 a.m.