Triple
T37736188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Truths doctrine |
E940281
|
entity |
| Predicate | goalWithin |
P100703
|
FINISHED |
| Object | clarifying path to enlightenment |
—
|
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: clarifying path to enlightenment | Statement: [Two Truths doctrine, goalWithin, clarifying path to enlightenment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalWithin Context triple: [Two Truths doctrine, goalWithin, clarifying path to enlightenment]
-
A.
goalIn
chosen
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
D.
goalAtEnd
Indicates that a particular goal or objective holds true or is achieved at the final state or endpoint of a process, sequence, or event.
-
E.
goalImposedOn
Indicates that a specific goal or objective is assigned or mandated by one entity for another entity to pursue or achieve.
- 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.