Triple
T11674222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ānanda |
E277450
|
entity |
| Predicate | positionInSaṅgha |
P37071
|
FINISHED |
| Object | one of the Buddha’s closest attendants |
—
|
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: one of the Buddha’s closest attendants | Statement: [Ānanda, positionInSaṅgha, one of the Buddha’s closest attendants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSaṅgha Context triple: [Ānanda, positionInSaṅgha, one of the Buddha’s closest attendants]
-
A.
roleInNobleEightfoldPath
Indicates the specific function or contribution that something has within the structure or practice of the Noble Eightfold Path.
-
B.
roleInMonasticism
chosen
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
C.
positionInJainTradition
Indicates the role, rank, or status an entity holds within the hierarchy or lineage of the Jain religious tradition.
-
D.
positionInPrayer
Indicates the specific posture or stage a participant occupies within the sequence of actions in a prayer.
-
E.
roleAtTemple
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.