Triple
T26351956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Ascetics |
E662924
|
entity |
| Predicate | originallyPracticed |
P191336
|
FINISHED |
| Object | severe asceticism |
—
|
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: severe asceticism | Statement: [Five Ascetics, originallyPracticed, severe asceticism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyPracticed Context triple: [Five Ascetics, originallyPracticed, severe asceticism]
-
A.
wasFirstPracticedIn
Indicates that an activity, custom, or practice originated or was initially carried out in a particular place or time.
-
B.
practicedUnder
Indicates that one entity gained experience or training while working under the guidance, supervision, or mentorship of another entity.
-
C.
stillPracticedAs
Indicates that a tradition, custom, or practice continues to be actively carried out in a specified place, time, or context.
-
D.
isPracticedAt
Indicates that an activity, skill, or discipline is regularly performed or carried out at a particular location or context.
-
E.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
- 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_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 26, 2026, 10:46 p.m.