Triple
T6567233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Walad |
E153937
|
entity |
| Predicate | roleInOrder |
P46813
|
FINISHED |
| Object | organizer of the Mevlevi Order |
—
|
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: organizer of the Mevlevi Order | Statement: [Sultan Walad, roleInOrder, organizer of the Mevlevi Order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInOrder Context triple: [Sultan Walad, roleInOrder, organizer of the Mevlevi Order]
-
A.
roleInSpecification
Indicates that an entity participates in a specification with a particular role or function within that specification.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
roleInAmazon
Indicates that one entity holds a specific role, position, or function within Amazon in relation to the other entity.
-
E.
roleInCommandStructure
chosen
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
- 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.