Triple
T37349578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushaf al-Madina |
E927284
|
entity |
| Predicate | followsOrthography |
P29676
|
FINISHED |
| Object | Uthmani orthography |
—
|
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: Uthmani orthography | Statement: [Mushaf al-Madina, followsOrthography, Uthmani orthography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsOrthography Context triple: [Mushaf al-Madina, followsOrthography, Uthmani orthography]
-
A.
usesStandardOrthographyOf
chosen
Indicates that one entity writes or represents language according to the standard orthographic system defined for another entity.
-
B.
orthographicIndependence
Indicates that one writing system or orthographic form functions independently of, and is not derived from or constrained by, another.
-
C.
hasOrthographicConvention
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
-
D.
orthographyNote
Indicates that there is a note or comment about the spelling or written form of an entity’s name or label.
-
E.
roleInOrthography
Indicates the specific function or contribution an element has within a given writing system or orthographic structure.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:16 p.m.