Triple
T30534351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golconda diamonds |
E777097
|
entity |
| Predicate | historicallyTradedThrough |
P58558
|
FINISHED |
| Object | Golconda fort market |
—
|
NE NERFINISHED |
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: Golconda fort market | Statement: [Golconda diamonds, historicallyTradedThrough, Golconda fort market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyTradedThrough Context triple: [Golconda diamonds, historicallyTradedThrough, Golconda fort market]
-
A.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
B.
tradedUsing
Indicates that an exchange or trade was conducted by means of a specified instrument, medium, or mechanism.
-
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.
tradeItemsHistorically
chosen
Indicates that the entities have engaged in trading items with each other at some point in the past.
-
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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 29, 2026, 8:18 p.m.