Triple
T6567263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Walad |
E153937
|
entity |
| Predicate | aimOfWritings |
P22267
|
FINISHED |
| Object | to explain and systematize Rumi’s teachings |
—
|
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: to explain and systematize Rumi’s teachings | Statement: [Sultan Walad, aimOfWritings, to explain and systematize Rumi’s teachings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfWritings Context triple: [Sultan Walad, aimOfWritings, to explain and systematize Rumi’s teachings]
-
A.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
literaryPurpose
chosen
Indicates the intended function, effect, or communicative goal that a text or passage is meant to achieve within a literary context.
-
C.
editorialGoal
Indicates that one entity has the role or purpose of serving as an editorial objective or target for another entity.
-
D.
writingFocus
Indicates that an entity’s primary attention or effort is directed toward writing or written expression.
-
E.
aimsToInform
Indicates an action whose purpose is to provide information or increase the knowledge of a target.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.