Triple
T5836997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichfield literary circle |
E129496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century cultural group |
C1971
|
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: 18th-century cultural group Context triple: [Lichfield literary circle, instanceOf, 18th-century cultural group]
-
A.
18th-century organization
chosen
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
-
B.
17th-century movement
A 17th-century movement is a historically situated collective trend or initiative—cultural, intellectual, political, religious, or artistic—that emerged and developed primarily during the 1600s, shaping and reflecting the values and conflicts of that era.
-
C.
18th-century person
A person who lived during the 18th century, typically shaped by the social, political, and cultural contexts of that era, including Enlightenment ideas, colonial expansion, and early industrialization.
-
D.
18th-century art event
An 18th-century art event is a historically situated gathering, exhibition, performance, or public display centered on the creation, presentation, or discussion of visual or decorative arts produced during the 1700s.
-
E.
early 18th-century conflict
An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:54 p.m.