Triple
T37733558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arahant |
E940221
|
entity |
| Predicate | hasFettersRemoved |
P192737
|
FINISHED |
| Object | all ten fetters |
—
|
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: all ten fetters | Statement: [arahant, hasFettersRemoved, all ten fetters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFettersRemoved Context triple: [arahant, hasFettersRemoved, all ten fetters]
-
A.
freedFromCorruptionBy
Indicates that an entity was previously corrupted or tainted and was restored or purified through the actions or influence of another entity.
-
B.
willBreakFreeDuring
Indicates that an entity is expected to escape or become free from another entity or constraint during a specified time or event.
-
C.
hasBodhisattva
Indicates that one entity includes, is associated with, or is characterized by the presence or guidance of a bodhisattva.
-
D.
cannotBeLeashed
Indicates that one entity is not allowed or not able to be restrained, controlled, or attached using a leash by another entity.
-
E.
hasOldSanctuary
Indicates that an entity possesses or is associated with an old or former sanctuary.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:18 p.m.