Triple
T29656134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenaby |
E750267
|
entity |
| Predicate | governedByParish |
P2739
|
FINISHED |
| Object | Malew Parish Commissioners |
—
|
NE NERFINISHED |
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: Malew Parish Commissioners | Statement: [Grenaby, governedByParish, Malew Parish Commissioners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByParish Context triple: [Grenaby, governedByParish, Malew Parish Commissioners]
-
A.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
B.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
C.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
D.
parish
chosen
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
E.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: April 28, 2026, 6:55 p.m.