Triple

T36254687
Position Surface form Disambiguated ID Type / Status
Subject al-lawh al-mahfuz E891900 entity
Predicate hasMetaphoricalDescription P81126 FINISHED
Object tablet 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: tablet | Statement: [al-lawh al-mahfuz, hasMetaphoricalDescription, tablet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMetaphoricalDescription
Context triple: [al-lawh al-mahfuz, hasMetaphoricalDescription, tablet]
  • A. hasMetaphoricalForm chosen
    Indicates that one entity is expressed, represented, or understood through a metaphorical form or figurative expression involving another entity.
  • B. hasMetaphoricalContent
    Indicates that something contains or expresses meaning through metaphorical, rather than purely literal, content.
  • C. hasMetaphoricalSubject
    Indicates that one entity functions as the metaphorical subject or source domain in a figurative or metaphorical expression involving another entity.
  • D. hasMetaphoricalFramework
    Indicates that one entity employs or is structured around a metaphorical framework derived from or associated with another entity.
  • E. hasMetaphorType
    Indicates that one entity is classified as having or using a particular type of metaphor in relation to another 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_69f76e4599108190811532e707d6bc2c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ff5803c02c81908b63067119f5e684 completed May 9, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69ff576d8b308190b49a1e072a0ae661 completed May 9, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:09 p.m.