Triple
T25445230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roudham |
E637616
|
entity |
| Predicate | mergedParishWith |
P56474
|
FINISHED |
| Object | Larling |
—
|
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: Larling | Statement: [Roudham, mergedParishWith, Larling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedParishWith Context triple: [Roudham, mergedParishWith, Larling]
-
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.
parishWith
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
-
C.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
D.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
-
E.
formsCivilParishWith
chosen
Indicates that two or more entities are administratively combined to constitute a single 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f70346cc8190b7ed6b5a86a508cd |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:01 p.m.