Triple
T35165625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Althorpe |
E1015393
|
entity |
| Predicate | isPartOfCivilParish |
P178050
|
FINISHED |
| Object | Keadby with Althorpe |
—
|
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: Keadby with Althorpe | Statement: [Althorpe, isPartOfCivilParish, Keadby with Althorpe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCivilParish Context triple: [Althorpe, isPartOfCivilParish, Keadby with Althorpe]
-
A.
onlyCivilParishOf
Indicates that one entity is the sole civil parish associated with, or contained within, the other entity, with no other civil parishes sharing that association.
-
B.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
C.
hasCivilParishComponent
chosen
Indicates that an entity includes or is composed of the specified civil parish as one of its administrative components.
-
D.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
E.
civilParishFor
Indicates that one entity is the civil parish to which another entity (such as a place or administrative area) belongs or is assigned.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.