Triple
T2445692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirk Session |
E53387
|
entity |
| Predicate | governsTypeOfBody |
P18964
|
FINISHED |
| Object | parish church congregation |
—
|
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: parish church congregation | Statement: [Kirk Session, governsTypeOfBody, parish church congregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTypeOfBody Context triple: [Kirk Session, governsTypeOfBody, parish church congregation]
-
A.
governingBodyOfType
chosen
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
B.
governingBody2
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
C.
establishesBodyType
Indicates that an entity defines or sets the physical or structural body type of another entity.
-
D.
governmentBodyType
Indicates the classification or category of a governmental organization based on its structural or functional role.
-
E.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.