Triple
T16934172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sufi orders |
E410787
|
entity |
| Predicate | havePurpose |
P79
|
FINISHED |
| Object | achieving closeness to God |
—
|
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: achieving closeness to God | Statement: [Sufi orders, havePurpose, achieving closeness to God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: havePurpose Context triple: [Sufi orders, havePurpose, achieving closeness to God]
-
A.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
B.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
C.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
-
D.
meetsForPurpose
Indicates that one entity meets with another specifically to pursue or accomplish a particular purpose or objective.
-
E.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2714b08190a2524d5d9578cc87 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.