Triple
T23952312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intihā-nāma |
E603080
|
entity |
| Predicate | associatedWithSufiOrder |
P2830
|
FINISHED |
| Object | Mevlevi order |
—
|
NE NERFINISHED |
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: Mevlevi order | Statement: [Intihā-nāma, associatedWithSufiOrder, Mevlevi order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSufiOrder Context triple: [Intihā-nāma, associatedWithSufiOrder, Mevlevi order]
-
A.
associatedOrderFoundedIn
Indicates that an order or organization associated with an entity was founded in a specified place or time.
-
B.
associatedWithImamNumber
Indicates a relationship where an entity is linked to, or identified by, a specific numbered Imam in a sequence of Imams.
-
C.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
-
D.
establishedWithOrder
Indicates that something is created, initiated, or set up in accordance with a specified order or sequence.
-
E.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d48bc881909d58d258757e67ad |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:20 p.m.