Triple
T4911875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horsham District |
E110250
|
entity |
| Predicate | hasParishStructure |
P21036
|
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: [Horsham District, hasParishStructure, civil parishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishStructure Context triple: [Horsham District, hasParishStructure, civil parishes]
-
A.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
B.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
C.
hasParishCouncils
chosen
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
D.
hasParishType
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
E.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.