Triple
T7160153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Laurens & Company |
E166921
|
entity |
| Predicate | handledCommodity |
P44036
|
FINISHED |
| Object | enslaved people |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: enslaved people | Statement: [Henry Laurens & Company, handledCommodity, enslaved people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledCommodity Context triple: [Henry Laurens & Company, handledCommodity, enslaved people]
-
A.
handlesCommodity
chosen
Indicates that one entity is responsible for dealing with, managing, or processing a particular commodity in some operational or transactional capacity.
-
B.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
C.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
D.
importedCommodity
Indicates that a commodity has been brought into a country or region from abroad through import activities.
-
E.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
- F. None of above.
Provenance (3 batches)
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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e811d6b081909dafeee1d820c74f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.