Triple

T10864379
Position Surface form Disambiguated ID Type / Status
Subject The Iron E256488 entity
Predicate hasOrderInMushaf P26532 FINISHED
Object 57 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: 57 | Statement: [The Iron, hasOrderInMushaf, 57]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrderInMushaf
Context triple: [The Iron, hasOrderInMushaf, 57]
  • A. hasPageRangeInMushaf
    Indicates that a text segment spans a specific range of pages within a particular mushaf (written copy of the Quran).
  • B. foundInMushaf
    Indicates that something (such as a verse, phrase, or reading) is present and recorded in the written text of the Mushaf (the compiled Qur’anic codex).
  • C. positionInMushaf chosen
    Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
  • D. hasVerseOrder
    Indicates that one verse is ordered or sequenced in relation to another verse within a structured text.
  • E. hasPositionInBook
    Indicates that an entity occupies a specific position or location within a book.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7516b2f148190adbacd35fc8c2056 completed April 9, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69d70d308dfc81908792f98cfb871392 completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:20 p.m.