Triple
T18237287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dix, Edwards & Co. |
E436714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century publishing firm |
C39492
|
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: 19th-century publishing firm Context triple: [Dix, Edwards & Co., instanceOf, 19th-century publishing firm]
-
A.
publishing organization
A publishing organization is an entity that selects, produces, and distributes content such as books, journals, or digital media to reach and inform a target audience.
-
B.
Jewish publisher
A Jewish publisher is an individual or organization, often rooted in Jewish cultural or religious traditions, that selects, produces, and disseminates written or digital works related to Jewish life, history, religion, or broader topics of interest to Jewish communities.
-
C.
publishing company imprint
A publishing company imprint is a trade name or brand under which a publisher releases specific categories or lines of books, often to target particular markets or audiences while remaining part of the larger parent company.
-
D.
Lutheran publisher
A Lutheran publisher is an organization that produces, distributes, and promotes books, periodicals, and other media that reflect and support Lutheran theology, worship, education, and devotional life.
-
E.
19th-century British company
chosen
A 19th-century British company is a business organization established in Britain between 1801 and 1900, typically operating under early industrial capitalism, imperial trade networks, and evolving corporate and legal frameworks of the Victorian era.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:33 a.m.