Triple

T7498207
Position Surface form Disambiguated ID Type / Status
Subject Saint-Sulpice E177185 entity
Predicate religiousCenteredOn P17002 FINISHED
Object Roman Catholic parish of Saint‑Sulpice 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: Roman Catholic parish of Saint‑Sulpice | Statement: [Saint-Sulpice, religiousCenteredOn, Roman Catholic parish of Saint‑Sulpice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousCenteredOn
Context triple: [Saint-Sulpice, religiousCenteredOn, Roman Catholic parish of Saint‑Sulpice]
  • A. tookPlaceAtReligiousCenter
    Indicates that an event or action occurred at a religious center or place of worship.
  • B. ecclesiasticalCenter
    Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
  • C. spiritualCenterOf chosen
    Indicates that one entity serves as the primary locus or focal point of spiritual life, practice, or significance for another entity or group.
  • D. isPlaceOfWorshipFor
    Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
  • E. nearReligiousSite
    Indicates that one entity is located close to or in the immediate vicinity of a religious site.
  • 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_69c69f2696688190915a8458f2398211 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f81b431481908214b69c6c8d83bc completed March 27, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69c6f4d266d88190982cf5d2ee2e9564 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:44 p.m.