Triple
T8769912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rymättylä |
E208430
|
entity |
| Predicate | Rymättylä Church |
P15000
|
FINISHED |
| Object | Lutheran 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: Lutheran church | Statement: [Rymättylä, Rymättylä Church, Lutheran church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Rymättylä Church Context triple: [Rymättylä, Rymättylä Church, Lutheran church]
-
A.
hasChurch
chosen
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
C.
formerCathedral
Indicates that a building once held the status and function of a cathedral but no longer does.
-
D.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
-
E.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5eedc7188190a67d959b9af53837 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.