Triple

T30692385
Position Surface form Disambiguated ID Type / Status
Subject Pitareti E781363 entity
Predicate religiousHeritageNearby P29505 FINISHED
Object medieval Georgian Orthodox monastery 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: medieval Georgian Orthodox monastery | Statement: [Pitareti, religiousHeritageNearby, medieval Georgian Orthodox monastery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousHeritageNearby
Context triple: [Pitareti, religiousHeritageNearby, medieval Georgian Orthodox monastery]
  • A. nearReligiousSite chosen
    Indicates that one entity is located close to or in the immediate vicinity of a religious site.
  • B. religiousTextAssociationNearby
    Indicates a spatial relationship where a religious text or related object is located close to or in the immediate vicinity of another entity.
  • C. hasPlaceOfWorship
    Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
  • D. traditionalReligionPlace
    Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
  • E. placeOfWorshipLocation
    Indicates the location where a particular place of worship is situated or found.
  • 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_69f224ab24e08190991d6edb6df58e8b completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe59d11e9881909d2f33b7c717030e completed May 8, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69fe394fdfbc8190a931926ae3635cbf completed May 8, 2026, 7:28 p.m.
Created at: April 29, 2026, 8:33 p.m.