Triple
T11826394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nibbana |
E281268
|
entity |
| Predicate | ultimateGoalFor |
P32840
|
FINISHED |
| Object | Theravada practitioners |
—
|
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: Theravada practitioners | Statement: [Nibbana, ultimateGoalFor, Theravada practitioners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateGoalFor Context triple: [Nibbana, ultimateGoalFor, Theravada practitioners]
-
A.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
B.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
C.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
D.
statedAsGoalFor
chosen
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
E.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5ec3a148190bb184ba0d481b16a |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.