Triple
T34075944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahaj Path |
E873907
|
entity |
| Predicate | completionPattern |
P128015
|
FINISHED |
| Object | can be completed over days |
—
|
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: can be completed over days | Statement: [Sahaj Path, completionPattern, can be completed over days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionPattern Context triple: [Sahaj Path, completionPattern, can be completed over days]
-
A.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
B.
completionBehavior
chosen
Indicates how an entity behaves or what outcome occurs when a process, task, or interaction reaches completion.
-
C.
finishPattern
Indicates that one entity completes or brings to an end a pattern initiated or followed by another entity.
-
D.
completionRelatedTo
Indicates that one entity’s completion, fulfillment, or finishing is connected to, dependent on, or relevant for another entity.
-
E.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:52 a.m.