Triple

T31771129
Position Surface form Disambiguated ID Type / Status
Subject Chaldoran E810940 entity
Predicate hasReligionSiteNearby P916 FINISHED
Object St. Thaddeus Monastery E232119 NE 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: St. Thaddeus Monastery | Statement: [Chaldoran, hasReligionSiteNearby, St. Thaddeus Monastery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReligionSiteNearby
Context triple: [Chaldoran, hasReligionSiteNearby, St. Thaddeus Monastery]
  • A. nearReligiousSite
    Indicates that one entity is located close to or in the immediate vicinity of a religious site.
  • B. hasReligiousSite chosen
    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.
  • C. religiousTextAssociationNearby
    Indicates a spatial relationship where a religious text or related object is located close to or in the immediate vicinity of another entity.
  • D. hasNearbyPilgrimageSite
    Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
  • E. traditionalReligionPlace
    Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
  • F. None of above.

Provenance (4 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_69f348e463e08190b902d4819195e1f0 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a019dfc69fc8190b0d80279a6216ba7 completed May 11, 2026, 9:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2d9d5058a48190b21b7ff16fb16c3a completed June 13, 2026, 6:11 p.m.
PD Predicate disambiguation batch_6a019d54586c81908292d4880db9fad2 completed May 11, 2026, 9:11 a.m.
Created at: April 30, 2026, 11:33 p.m.