Triple
T1151295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malabar Coast |
E23682
|
entity |
| Predicate | historicallyTradedWith |
P12536
|
FINISHED |
| Object | Arab merchants |
—
|
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: Arab merchants | Statement: [Malabar Coast, historicallyTradedWith, Arab merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyTradedWith Context triple: [Malabar Coast, historicallyTradedWith, Arab merchants]
-
A.
historicTradeRole
Indicates that an entity historically functioned as a significant participant or hub in trade or commercial exchange.
-
B.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
-
C.
hasTrade
chosen
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
-
E.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.