Triple
T11107966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolsa de Valores de Montevideo |
E262681
|
entity |
| Predicate | hasTradingInstrument |
P67141
|
FINISHED |
| Object | stocks |
—
|
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: stocks | Statement: [Bolsa de Valores de Montevideo, hasTradingInstrument, stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTradingInstrument Context triple: [Bolsa de Valores de Montevideo, hasTradingInstrument, stocks]
-
A.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
-
B.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
C.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
D.
hasFinancialInstrumentType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
-
E.
hasTradingVenueCode
Indicates that an entity is associated with a specific trading venue through its designated code.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a67d10c8190815d4c27d55270e8 |
completed | April 9, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.