Triple
T34140236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Église Saint-Laurent de Mehun-sur-Yèvre |
E875694
|
entity |
| Predicate | primaryParishChurchOf |
P108424
|
FINISHED |
| Object | Mehun-sur-Yèvre |
E250378
|
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: Mehun-sur-Yèvre | Statement: [Église Saint-Laurent de Mehun-sur-Yèvre, primaryParishChurchOf, Mehun-sur-Yèvre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryParishChurchOf Context triple: [Église Saint-Laurent de Mehun-sur-Yèvre, primaryParishChurchOf, Mehun-sur-Yèvre]
-
A.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
B.
parishChurchName
Indicates the name of the parish church associated with a given entity.
-
C.
isParishChurchIn
chosen
Indicates that a church serves as the designated parish church for a specific parish or locality.
-
D.
principalChurchOf
Indicates that one church serves as the main or most important church associated with a particular entity, such as a region, denomination, or institution.
-
E.
parishChurchDenomination
Indicates the religious denomination with which a parish church is formally affiliated.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37048228b881909db98f4b2035699f |
completed | June 20, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.