Triple
T26351979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Ascetics |
E662924
|
entity |
| Predicate | preConversionPractice |
P160577
|
FINISHED |
| Object | self-mortification |
—
|
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: self-mortification | Statement: [Five Ascetics, preConversionPractice, self-mortification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preConversionPractice Context triple: [Five Ascetics, preConversionPractice, self-mortification]
-
A.
partialConversion
Indicates that one entity is transformed into another only to some extent, so that the original is not fully converted or replaced.
-
B.
involvesConversionTo
Indicates that one entity undergoes a change of form, type, or state resulting in another entity.
-
C.
alsoPractice
Indicates that an entity engages in the same practice or activity as another entity, in addition to any other practices it may have.
-
D.
prevede
Indicates that an entity plans, foresees, or provides in advance for another entity, event, or outcome.
-
E.
memorizationPractice
Indicates engaging in activities or exercises specifically intended to commit information to memory or strengthen recall.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fec2c3c8190b76c15fa8a97f0e6 |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 10:46 p.m.