Triple
T11651327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRVG |
E276909
|
entity |
| Predicate | isTradableOn |
P6939
|
FINISHED |
| Object | electronic trading platforms |
—
|
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: electronic trading platforms | Statement: [TRVG, isTradableOn, electronic trading platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTradableOn Context triple: [TRVG, isTradableOn, electronic trading platforms]
-
A.
tradedOn
chosen
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
B.
notFreelyTradableInOffshoreMarkets
Indicates that the asset or instrument cannot be bought or sold without restriction in offshore or foreign markets.
-
C.
usedForTrading
Indicates that one entity serves as a medium, instrument, or item exchanged in commercial or barter transactions involving another entity.
-
D.
isTradingCenter
Indicates that a place functions as a central hub where goods, services, or financial instruments are actively exchanged or traded.
-
E.
isOptionsTraded
Indicates that options contracts based on the referenced entity are actively traded in a financial market.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.