Triple
T1089555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smyrna |
E24129
|
entity |
| Predicate | tradeNetwork |
P23353
|
FINISHED |
| Object | Mediterranean trade routes |
—
|
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: Mediterranean trade routes | Statement: [Smyrna, tradeNetwork, Mediterranean trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeNetwork Context triple: [Smyrna, tradeNetwork, Mediterranean trade routes]
-
A.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
B.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
C.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
D.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
E.
supplyChain
Indicates a relationship where one entity participates in providing, transferring, or managing goods, services, or information to another as part of a sequential production and distribution process.
- F. None of above. chosen
Provenance (4 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97f216881909e9b8943ce2078e4 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:42 p.m.