Triple
T26351973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Ascetics |
E662924
|
entity |
| Predicate | afterConversionStatus |
P57908
|
FINISHED |
| Object | arahants |
—
|
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: arahants | Statement: [Five Ascetics, afterConversionStatus, arahants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterConversionStatus Context triple: [Five Ascetics, afterConversionStatus, arahants]
-
A.
afterConversionKnownAs
Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
-
B.
conversionCompleted
Indicates that a previously initiated conversion process has finished successfully.
-
C.
conversionStatus
chosen
Indicates the current state or outcome of a process in which one entity is transformed, converted, or transitioned into another form or status.
-
D.
hasConvertedTo
Indicates that an entity has changed its previous state, status, form, or affiliation into a new one.
-
E.
functionAfterConversion
Indicates that one function or behavior occurs as a result of, or is valid only after, a specified conversion has taken place.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 10:46 p.m.