Triple
T30332848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Margaret’s Church, Airdrie |
E771533
|
entity |
| Predicate | hasParishOrganisation |
P196177
|
FINISHED |
| Object | parish council |
—
|
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 council | Statement: [St Margaret’s Church, Airdrie, hasParishOrganisation, parish council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOrganisation Context triple: [St Margaret’s Church, Airdrie, hasParishOrganisation, parish council]
-
A.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
B.
hasParishNetwork
Indicates that an entity is connected to or served by a specific parish or group of parishes within an ecclesiastical or community network.
-
C.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
D.
hasParishLevel
Indicates that an entity is associated with or classified according to a specific parish-level administrative or ecclesiastical unit.
-
E.
haveOwnParishes
Indicates that an entity possesses or is responsible for its own distinct parishes.
- F. None of above. chosen
Provenance (4 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_69fe12a769c08190bc445d302d2e8f98 |
completed | May 8, 2026, 4:43 p.m. |
Created at: April 29, 2026, 7:53 p.m.