Triple
T24625562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk was not captured by the British in 1813 |
E609530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical outcome |
C17292
|
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 outcome Context triple: [Norfolk was not captured by the British in 1813, instanceOf, historical outcome]
-
A.
historical event aftermath
chosen
The historical event aftermath is the period and set of consequences that follow a significant occurrence, encompassing its social, political, economic, and cultural impacts over time.
-
B.
historical process
A historical process is a sequence of interconnected events and developments over time through which social, political, economic, or cultural conditions gradually change.
-
C.
historical policy
Historical policy is a conceptual class encompassing formal rules, laws, and governance decisions implemented in the past that shaped societal, economic, and political developments over time.
-
D.
historical position
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
E.
historical axis
A historical axis is a conceptual timeline or reference line that organizes events, periods, or developments in chronological order to reveal patterns and relationships across history.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:32 a.m.