Triple
T20982240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early modern London |
E516794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical period of London |
C138
|
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: historical period of London Context triple: [Early modern London, instanceOf, historical period of London]
-
A.
historical city period
A historical city period is a span of time in a city's past characterized by distinctive social, political, economic, and cultural conditions that shape its development and identity.
-
B.
historical period
chosen
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
C.
era of English history
An era of English history is a distinct period characterized by particular political structures, social conditions, cultural developments, and significant events that collectively differentiate it from other times in England’s past.
-
D.
history of the United Kingdom
The history of the United Kingdom traces the political, social, economic, and cultural development of England, Scotland, Wales, and Northern Ireland from their early origins through unification, empire, conflict, and modern democracy.
-
E.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:48 p.m.