Triple
T23226080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maddington, Wiltshire |
E581015
|
entity |
| Predicate | mergedIntoParishDate |
P50534
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [Maddington, Wiltshire, mergedIntoParishDate, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedIntoParishDate Context triple: [Maddington, Wiltshire, mergedIntoParishDate, 1934]
-
A.
formerCivilParishMergedInto
Indicates that a former civil parish has been administratively combined into another civil parish or local government unit, ceasing to exist as a separate entity.
-
B.
incorporatedIntoOnDate
chosen
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
C.
isHistoricParishOf
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
D.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
E.
formerCivilParish
Indicates that an entity was once designated as a civil parish but no longer holds that administrative status.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922e2d2c81908c0f3fa5df8a5c58 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.