Triple
T7683316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shia Sufism |
E174047
|
entity |
| Predicate | hasDebateWithin |
P15176
|
FINISHED |
| Object | legitimacy of Sufi orders |
—
|
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: legitimacy of Sufi orders | Statement: [Shia Sufism, hasDebateWithin, legitimacy of Sufi orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebateWithin Context triple: [Shia Sufism, hasDebateWithin, legitimacy of Sufi orders]
-
A.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
B.
hasDebatedPerson
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
C.
hasDebatedStatus
Indicates that an entity has participated in or been assigned a particular status related to a debate or debating activity.
-
D.
hasNotableDebates
Indicates that there have been significant or widely recognized debates or controversies involving the related entities.
-
E.
hasLongTermDebateOn
chosen
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.