Triple
T36256092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristelmestune |
E891940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval place name |
C4613
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval place name Context triple: [Bristelmestune, instanceOf, medieval place name]
-
A.
historical place name
chosen
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
B.
medieval English name
A medieval English name is a personal name used in England roughly between the 5th and 15th centuries, often reflecting Old English, Norman, or Latin influences and frequently tied to religious, occupational, or locational origins.
-
C.
medieval byname
A medieval byname is an additional personal identifier used in the Middle Ages, often describing a person’s occupation, origin, physical trait, or reputation, which could later develop into a hereditary surname.
-
D.
medieval Latin name
A medieval Latin name is a personal or place designation used in the Middle Ages, typically rendered in Latinized form to align with ecclesiastical, scholarly, or administrative conventions of the period.
-
E.
medieval county
A medieval county is a territorial and administrative unit governed by a count or similar noble, encompassing lands, settlements, and jurisdictions within a feudal hierarchy.
- F. None of above.
Provenance (1 batch)
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.