Triple
T37733539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arahant |
E940221
|
entity |
| Predicate | hasStatusInEarlyBuddhism |
P35203
|
FINISHED |
| Object | primary goal of the path |
—
|
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: primary goal of the path | Statement: [arahant, hasStatusInEarlyBuddhism, primary goal of the path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInEarlyBuddhism Context triple: [arahant, hasStatusInEarlyBuddhism, primary goal of the path]
-
A.
statusInBuddhism
Indicates the recognized role, standing, or significance an entity holds within Buddhist doctrine, practice, or community.
-
B.
earliestAttestedStatus
Indicates the earliest known or recorded status that has been documented for an entity.
-
C.
hasStatusInTradition
chosen
Indicates that an entity holds a particular recognized status or standing within a specified tradition or traditional framework.
-
D.
equivalentInBuddhism
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
-
E.
hasBuddhistTerm
Indicates that one entity includes, references, or is associated with a term originating from or used within Buddhism.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:18 p.m.