Triple

T30638031
Position Surface form Disambiguated ID Type / Status
Subject Apedemak temple E779896 entity
Predicate partOfSiteComplex P196418 FINISHED
Object Musawwarat es-Sufra temple complex 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: Musawwarat es-Sufra temple complex | Statement: [Apedemak temple, partOfSiteComplex, Musawwarat es-Sufra temple complex]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partOfSiteComplex
Context triple: [Apedemak temple, partOfSiteComplex, Musawwarat es-Sufra temple complex]
  • A. partOfSite chosen
    Indicates that one entity is a physical or logical component contained within or belonging to a larger site or location.
  • B. partOfTerminalComplex
    Indicates that an entity functions as a component or subunit within a larger terminal complex structure.
  • C. partOfDynasticComplex
    Indicates that one entity is a constituent element or subdivision within a larger dynastic complex or ruling lineage structure.
  • D. housedWithinComplex
    Indicates that one entity is located inside and functionally part of a larger building or facility complex.
  • E. nearbySitePartOf
    Indicates that one site or site component is located close to and is considered part of another, larger site or site component.
  • 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_69f224a50ebc81909b961a94c7f66b12 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ff1a972bf08190860696ffcd887c0f completed May 9, 2026, 11:29 a.m.
PD Predicate disambiguation batch_69ff184005d88190bf38283ebc499b28 completed May 9, 2026, 11:19 a.m.
Created at: April 29, 2026, 8:29 p.m.