Triple
T33884232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Antoniuskerk in Rijen |
E868580
|
entity |
| Predicate | isCentralParishChurchOf |
P108424
|
FINISHED |
| Object | Rijen |
—
|
NE NERFINISHED |
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: Rijen | Statement: [St. Antoniuskerk in Rijen, isCentralParishChurchOf, Rijen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralParishChurchOf Context triple: [St. Antoniuskerk in Rijen, isCentralParishChurchOf, Rijen]
-
A.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
B.
isParishChurchIn
chosen
Indicates that a church serves as the designated parish church for a specific parish or locality.
-
C.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
-
D.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
E.
hasReligiousParishCentre
Indicates that an entity has, is associated with, or is served by a specific religious parish center.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.