Triple
T11674266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Śāriputra |
E277451
|
entity |
| Predicate | attained |
P1518
|
FINISHED |
| Object | arahantship |
—
|
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: arahantship | Statement: [Śāriputra, attained, arahantship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attained Context triple: [Śāriputra, attained, arahantship]
-
A.
achieved
chosen
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
B.
passed
Indicates that one entity successfully transferred control, responsibility, or an item (such as an object, message, or test) to another entity or through a specified stage or condition.
-
C.
admitted
Indicates that one entity has formally accepted, acknowledged, or allowed another entity or fact, often into a place, group, or state.
-
D.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
E.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
- 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.