Triple
T35189494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glanford Brigg Rural District |
E1016080
|
entity |
| Predicate | containedParishType |
P13874
|
FINISHED |
| Object | civil parishes |
—
|
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: civil parishes | Statement: [Glanford Brigg Rural District, containedParishType, civil parishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedParishType Context triple: [Glanford Brigg Rural District, containedParishType, civil parishes]
-
A.
hasParishType
chosen
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
B.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
C.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
D.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
E.
hasParishLevel
Indicates that an entity is associated with or classified according to a specific parish-level administrative or ecclesiastical unit.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
Created at: May 3, 2026, 4:02 p.m.