Triple
T32045797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulayman ibn Surad al-Khuza‘i |
E818344
|
entity |
| Predicate | roleInKufa |
P201496
|
FINISHED |
| Object | leading pro-Alid notable |
—
|
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: leading pro-Alid notable | Statement: [Sulayman ibn Surad al-Khuza‘i, roleInKufa, leading pro-Alid notable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKufa Context triple: [Sulayman ibn Surad al-Khuza‘i, roleInKufa, leading pro-Alid notable]
-
A.
roleInSchibsted
Indicates that an entity holds or has held a specific role or position within the Schibsted organization.
-
B.
roleInArabStrap
Indicates that an entity holds or held a specific role or position within the band Arab Strap.
-
C.
roleInKuomboka
Indicates that an entity holds a specific role or function within the context of the Kuomboka ceremony or event.
-
D.
roleInMedina
Indicates the specific function, position, or responsibility an entity holds within the context of Medina.
-
E.
roleInKairouan
Indicates that an entity holds or held a specific role, position, or function in relation to Kairouan.
- F. None of above. chosen
Provenance (4 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: May 1, 2026, 12:20 a.m.