Triple
T37742970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabban |
E940767
|
entity |
| Predicate | canonicalReaderOf |
P189198
|
FINISHED |
| Object | Qurʾan |
—
|
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: Qurʾan | Statement: [Zabban, canonicalReaderOf, Qurʾan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalReaderOf Context triple: [Zabban, canonicalReaderOf, Qurʾan]
-
A.
canonicalReading
Indicates that one representation of a text or expression is the standard or authoritative version used for reading or interpretation of another.
-
B.
alternativeReader
Indicates that one entity serves as an alternative or substitute reader for another entity or resource.
-
C.
canonicalText
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
D.
canonicalFor
Indicates that one entity serves as the authoritative or standard representation for another, often consolidating or standing in for its variants or duplicates.
-
E.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:18 p.m.