Triple
T32160613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qur’an 46:35 |
E821413
|
entity |
| Predicate | canonicalTextLanguage |
P31857
|
FINISHED |
| Object | Classical Arabic |
—
|
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: Classical Arabic | Statement: [Qur’an 46:35, canonicalTextLanguage, Classical Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalTextLanguage Context triple: [Qur’an 46:35, canonicalTextLanguage, Classical Arabic]
-
A.
canonicalLanguage
Indicates that one entity is the officially recognized or standard language associated with another entity.
-
B.
canonicalText
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
C.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
D.
contentLanguage
chosen
Indicates the language in which the content is expressed or intended to be understood.
-
E.
primaryLanguageType
Indicates the main category or kind of language (such as spoken, written, or signed) that serves as the primary mode of communication in a given context or for a given entity.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:32 a.m.