Triple
T30776049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symington |
E783671
|
entity |
| Predicate | hasParishChurchListingCategory |
P196700
|
FINISHED |
| Object | Category A |
—
|
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: Category A | Statement: [Symington, hasParishChurchListingCategory, Category A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishChurchListingCategory Context triple: [Symington, hasParishChurchListingCategory, Category A]
-
A.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
-
B.
isActiveParishChurch
Indicates that a church currently functions as the main parish church for a community and is actively in use for parish activities and services.
-
C.
hasCathedralParish
Indicates that a cathedral is associated with or served by a specific parish within an ecclesiastical jurisdiction.
-
D.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
E.
hasAnglicanParishChurch
Indicates that an entity possesses or is served by a specific Anglican parish church.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: April 29, 2026, 8:40 p.m.