Triple
T26351971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Ascetics |
E662924
|
entity |
| Predicate | doctrineReceived |
P160996
|
FINISHED |
| Object | Middle Way |
—
|
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: Middle Way | Statement: [Five Ascetics, doctrineReceived, Middle Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineReceived Context triple: [Five Ascetics, doctrineReceived, Middle Way]
-
A.
doctrineOf
Indicates a relationship where one entity is the doctrinal teaching, principle, or belief system associated with, derived from, or formally held by another entity.
-
B.
doctrineHeld
Indicates that an agent adheres to, supports, or maintains a particular doctrine or set of principles.
-
C.
doctrineAddressed
Indicates that a particular doctrine is the topic or subject that is dealt with, discussed, or responded to by something (such as a text, statement, or decision).
-
D.
doctrineDiscussed
Indicates that a particular doctrine is the topic of discussion or analysis in a given context or interaction.
-
E.
doctrineBasisFor
Indicates that one doctrine serves as a foundational justification, support, or underlying basis for another doctrine or position.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fec2c3c8190b76c15fa8a97f0e6 |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 26, 2026, 10:46 p.m.