Triple
T19074864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Reconciliation |
E466877
|
entity |
| Predicate | pastoralSetting |
P66690
|
FINISHED |
| Object | parish |
—
|
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 | Statement: [First Reconciliation, pastoralSetting, parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastoralSetting Context triple: [First Reconciliation, pastoralSetting, parish]
-
A.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
-
B.
pastoralWorkLocation
chosen
Indicates the place where a person carries out their pastoral or ministerial duties.
-
C.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
-
D.
pastoralPurpose
Indicates that something is intended or designated for pastoral use, care, or ministry within a religious or spiritual context.
-
E.
semiRuralCharacter
Indicates that a place or area has characteristics intermediate between rural and urban, combining elements of both environments.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.