Triple
T36041806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warwick |
E1042560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic English 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: historic English place name Context triple: [Warwick, instanceOf, historic English 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.
Old English toponym
An Old English toponym is a place-name whose form and meaning originate from the Old English language, often reflecting early medieval landscape features, settlements, or ownership.
-
C.
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.
-
D.
historic county of England
A historic county of England is a traditional geographic and cultural subdivision whose boundaries were established for administrative, judicial, and social purposes before modern local government reforms.
-
E.
Brythonic toponym
A Brythonic toponym is a place name derived from the Brythonic branch of the Celtic languages, such as Welsh, Cornish, or Breton, often preserving ancient linguistic and cultural features in modern geography.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.