Triple
T10134363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red River trade |
E226818
|
entity |
| Predicate | keyCommodity |
P3553
|
FINISHED |
| Object | cotton |
—
|
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: cotton | Statement: [Red River trade, keyCommodity, cotton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCommodity Context triple: [Red River trade, keyCommodity, cotton]
-
A.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
B.
commodity
chosen
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
C.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
D.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
E.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cde87e1f908190a53865420f2b8f93 |
completed | April 2, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:06 p.m.