Triple
T34432655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sthānakavāsī |
E883868
|
entity |
| Predicate | monasticPractice |
P58096
|
FINISHED |
| Object | itinerant mendicancy |
—
|
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: itinerant mendicancy | Statement: [Sthānakavāsī, monasticPractice, itinerant mendicancy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticPractice Context triple: [Sthānakavāsī, monasticPractice, itinerant mendicancy]
-
A.
monasticTradition
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
B.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
-
C.
mendicantPractice
chosen
Indicates that an entity engages in the practice of begging or living by alms as a religious or spiritual discipline.
-
D.
monasticTrainingAt
Indicates that a person undergoes or has undergone monastic training at a particular religious institution or location.
-
E.
monasticCode
Indicates that an entity follows, is governed by, or is associated with a specific set of monastic rules or disciplinary code.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.