Triple
T11117119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middelstum |
E262914
|
entity |
| Predicate | HippolytuskerkInstanceOf |
P92816
|
FINISHED |
| Object | church |
—
|
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: church | Statement: [Middelstum, HippolytuskerkInstanceOf, church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HippolytuskerkInstanceOf Context triple: [Middelstum, HippolytuskerkInstanceOf, church]
-
A.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
B.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
C.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
D.
isTitularChurchOf
Indicates that a particular church holds the official honorary title associated with a specific cardinal or ecclesiastical office.
-
E.
religiousBuildingInstanceOf
chosen
Indicates that a specific religious building is an instance of a particular class or type of religious building.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af638b08190b7ade5eb0cab6b75 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.