Triple

T26138105
Position Surface form Disambiguated ID Type / Status
Subject منف E659435 entity
Predicate تضم_آثارًا P19329 FINISHED
Object تماثيل ضخمة لرمسيس الثاني 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: تماثيل ضخمة لرمسيس الثاني | Statement: [منف, تضم_آثارًا, تماثيل ضخمة لرمسيس الثاني]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: تضم_آثارًا
Context triple: [منف, تضم_آثارًا, تماثيل ضخمة لرمسيس الثاني]
  • A. نوع_آثار_مرتبط
    Indicates a relationship where one entity is associated with another through a specific type or category of related works or artifacts.
  • B. archaeologicalFindsInclude chosen
    Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
  • C. hasArchaeologicalMaterial
    Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
  • D. relicsAssociatedWith
    Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
  • E. hasArchaeologicalFeature
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or 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_69ee5bc3c20c8190bf2cf272f4170e95 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f60be1d2408190820365bf7d8436bd completed May 2, 2026, 2:36 p.m.
PD Predicate disambiguation batch_69f5b0021da88190bdd4cf2698c23edf completed May 2, 2026, 8:04 a.m.
Created at: April 26, 2026, 8:18 p.m.