Triple
T23365057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadras Dutch Fort |
E593292
|
entity |
| Predicate | tradingCommodity |
P3553
|
FINISHED |
| Object | textiles |
—
|
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: textiles | Statement: [Sadras Dutch Fort, tradingCommodity, textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingCommodity Context triple: [Sadras Dutch Fort, tradingCommodity, textiles]
-
A.
commodity
chosen
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
B.
otherCommodity
Indicates that an entity is associated with a commodity that is different from a primary, specified, or expected commodity in the given context.
-
C.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
D.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ab7fc481908b496ec9b543eddd |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.