Triple
T25978968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masulipatam |
E646017
|
entity |
| Predicate | wasTradingCenterFor |
P17489
|
FINISHED |
| Object | spices |
—
|
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: spices | Statement: [Masulipatam, wasTradingCenterFor, spices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTradingCenterFor Context triple: [Masulipatam, wasTradingCenterFor, spices]
-
A.
isTradingCenter
chosen
Indicates that a place functions as a central hub where goods, services, or financial instruments are actively exchanged or traded.
-
B.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
C.
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.
-
D.
tradedToOnDraftDay
Indicates that an entity (typically a player) was traded to another team specifically on the day of the draft.
-
E.
isTradedBy
Indicates that an item, asset, or resource is exchanged or dealt with by a particular agent, party, or trading 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6050d0a808190837a1fd676f604f4 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:53 a.m.