Triple

T21145754
Position Surface form Disambiguated ID Type / Status
Subject Nabataean religion E521049 entity
Predicate hasSacredArchitecture P64785 FINISHED
Object rock-cut temples 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: rock-cut temples | Statement: [Nabataean religion, hasSacredArchitecture, rock-cut temples]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSacredArchitecture
Context triple: [Nabataean religion, hasSacredArchitecture, rock-cut temples]
  • A. hasReligiousSite
    Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
  • B. hasTempleOf
    Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
  • C. hasRockCutTempleComplex chosen
    Indicates that an entity possesses or contains a complex of temples that have been carved directly into rock formations.
  • D. hasSacredSymbol
    Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
  • E. hasCultPlaceType
    Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
  • 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_69e0b50c6a848190a4e525a77a319b8a completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e723fcdb7c8190ae04d6ad9dff3187 completed April 21, 2026, 7:15 a.m.
PD Predicate disambiguation batch_69e5f5f8a5bc819081918c7fa8e4496d completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 2:58 p.m.