Triple
T27082779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Église Notre-Dame de Saint-Mandé |
E685943
|
entity |
| Predicate | hasParishActivity |
P109208
|
FINISHED |
| Object | Mass |
—
|
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: Mass | Statement: [Église Notre-Dame de Saint-Mandé, hasParishActivity, Mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishActivity Context triple: [Église Notre-Dame de Saint-Mandé, hasParishActivity, Mass]
-
A.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
B.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
C.
hasParishLife
chosen
Indicates that an entity maintains or supports organized parish-based religious and community life activities.
-
D.
isActiveParishChurch
Indicates that a church currently functions as the main parish church for a community and is actively in use for parish activities and services.
-
E.
hasPilgrimActivity
Indicates a relationship where an entity engages in or is associated with pilgrim-related activities, such as religious journeys, visits to sacred sites, or acts of pilgrimage.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 8:35 a.m.