Triple

T16523315
Position Surface form Disambiguated ID Type / Status
Subject Prophets in the drum of the dome E401373 entity
Predicate hasLocationInStructure P42732 FINISHED
Object drum of the dome 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: drum of the dome | Statement: [Prophets in the drum of the dome, hasLocationInStructure, drum of the dome]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocationInStructure
Context triple: [Prophets in the drum of the dome, hasLocationInStructure, drum of the dome]
  • A. hasLocationComponent chosen
    Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
  • B. locationOfStructure
    Indicates that a particular structure is situated at or occupies a specific location.
  • C. locatedOnStructureType
    Indicates that an entity is situated on or supported by a particular type of structure.
  • D. hasLocationRole
    Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
  • E. hasConceptualLocation
    Indicates that something is associated with or situated within a particular abstract, conceptual, or non-physical context or domain.
  • 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_69d883838abc8190bc79cb2d41733ce2 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32ed2622c8190b6429a49ca92284a completed April 18, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69e296995d388190b88ebe189dce890d completed April 17, 2026, 8:22 p.m.
Created at: April 10, 2026, 5:14 a.m.