Triple
T37733540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arahant |
E940221
|
entity |
| Predicate | attainsThrough |
P162788
|
FINISHED |
| Object | Noble Eightfold Path |
—
|
NE NERFINISHED |
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: Noble Eightfold Path | Statement: [arahant, attainsThrough, Noble Eightfold Path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attainsThrough Context triple: [arahant, attainsThrough, Noble Eightfold Path]
-
A.
achievedThrough
chosen
Indicates that a result, state, or outcome is brought about or realized by means of a specified method, process, or action.
-
B.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
C.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
D.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
E.
advancedThrough
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
- 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_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.