Triple
T30139353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibworth Beauchamp |
E766083
|
entity |
| Predicate | formsParishWith |
P56474
|
FINISHED |
| Object | Kibworth Harcourt |
—
|
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: Kibworth Harcourt | Statement: [Kibworth Beauchamp, formsParishWith, Kibworth Harcourt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsParishWith Context triple: [Kibworth Beauchamp, formsParishWith, Kibworth Harcourt]
-
A.
formsCivilParishWith
chosen
Indicates that two or more entities are administratively combined to constitute a single civil parish.
-
B.
parishWith
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
-
C.
civilParishGroupedWith
Indicates that two or more civil parishes are administratively associated or treated as a single grouped unit for certain official or organizational purposes.
-
D.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
E.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 7:17 p.m.