Triple
T29378548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Histon and Impington |
E745071
|
entity |
| Predicate | hasCivilParishComponent |
P178050
|
FINISHED |
| Object | Histon |
—
|
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: Histon | Statement: [Histon and Impington, hasCivilParishComponent, Histon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivilParishComponent Context triple: [Histon and Impington, hasCivilParishComponent, Histon]
-
A.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
B.
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.
-
C.
hasCivilParishName
Indicates that an entity has a specific civil parish name as its designated official name at the civil parish level.
-
D.
hasParishCouncils
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
E.
hasRuralParish
Indicates that an entity possesses or is associated with a rural parish as an administrative or ecclesiastical subdivision.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 28, 2026, 2:33 p.m.