Triple
T30685014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Tudor (Boston merchant) |
E781160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boston merchant |
C7999
|
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: Boston merchant Context triple: [Henry Tudor (Boston merchant), instanceOf, Boston merchant]
-
A.
18th-century Boston merchant
An 18th-century Boston merchant is a colonial-era trader who engaged in transatlantic and coastal commerce, dealing in goods like molasses, rum, textiles, and dry goods while navigating British imperial regulations and the growing tensions that led to the American Revolution.
-
B.
Italian merchant
An Italian merchant is a trader or businessperson from Italy who engages in the buying, selling, and distribution of goods, often across regional or international markets, to generate profit.
-
C.
Greek merchant
A Greek merchant is a trader from ancient or modern Greece who engages in the buying, selling, and transporting of goods across local and international markets, often serving as a key intermediary in Mediterranean commerce.
-
D.
New Englander
chosen
A New Englander is a person from the New England region of the northeastern United States, often associated with a distinct cultural identity shaped by the area's history, climate, and traditions.
-
E.
American boardinghouse owner
An American boardinghouse owner is a person who operates a residential establishment offering lodging, meals, and communal living arrangements—often on a weekly or monthly basis—to a diverse group of long-term or transient boarders.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.