Triple
T27092733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 15:45 |
E686212
|
entity |
| Predicate | canonicalTextOf |
P45461
|
FINISHED |
| Object | the Quran |
—
|
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: the Quran | Statement: [Quran 15:45, canonicalTextOf, the Quran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalTextOf Context triple: [Quran 15:45, canonicalTextOf, the Quran]
-
A.
canonicalText
chosen
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
B.
canonicalTextSection
Indicates that one text section is the authoritative or standard version associated with another representation or variant of that section.
-
C.
canonicalStatusIn
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
-
D.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
-
E.
textuallySystematizedBy
Indicates that information, concepts, or data are organized, structured, or codified into a systematic textual form by a particular agent or source.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:42 a.m.