Triple
T25514769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaundinya |
E639473
|
entity |
| Predicate | centralDoctrineUnderstood |
P4306
|
FINISHED |
| Object | Four Noble Truths |
—
|
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: Four Noble Truths | Statement: [Kaundinya, centralDoctrineUnderstood, Four Noble Truths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralDoctrineUnderstood Context triple: [Kaundinya, centralDoctrineUnderstood, Four Noble Truths]
-
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.
goalOfDoctrine
Indicates that a specified objective or end state is the intended goal or purpose of a particular doctrine.
-
C.
keyDoctrine
chosen
Indicates that something is a central or foundational doctrine within a belief system, organization, or theoretical framework.
-
D.
hasNumberOfDoctrines
Indicates the relationship that specifies how many doctrines are associated with a given entity.
-
E.
primaryDoctrine
Indicates that the object represents the main or foundational doctrine associated with the subject.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 2:55 p.m.