Triple
T34395063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul Gold Exchange |
E882805
|
entity |
| Predicate | tradingType |
P114890
|
FINISHED |
| Object | spot trading |
—
|
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: spot trading | Statement: [Istanbul Gold Exchange, tradingType, spot trading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingType Context triple: [Istanbul Gold Exchange, tradingType, spot trading]
-
A.
typeOfTrading
chosen
Indicates a relationship where one entity specifies the kind or category of trading activity associated with another entity.
-
B.
tradingMedium
Indicates that one entity serves as the medium or instrument through which another entity conducts trade or exchange.
-
C.
supportsTradingType
Indicates that one entity enables, allows, or is compatible with a specified type or mode of trading.
-
D.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
E.
tradingSegment
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 1:59 a.m.