Triple
T37777629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Sao_Paulo |
E941730
|
entity |
| Predicate | usedForStockExchange |
P35653
|
FINISHED |
| Object | B3 (Brasil Bolsa Balcão) |
—
|
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: B3 (Brasil Bolsa Balcão) | Statement: [America/Sao_Paulo, usedForStockExchange, B3 (Brasil Bolsa Balcão)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForStockExchange Context triple: [America/Sao_Paulo, usedForStockExchange, B3 (Brasil Bolsa Balcão)]
-
A.
usedByStockExchange
chosen
Indicates that something (such as a system, standard, or instrument) is utilized or adopted by a stock exchange in its operations or services.
-
B.
usedForTrading
Indicates that one entity serves as a medium, instrument, or item exchanged in commercial or barter transactions involving another entity.
-
C.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
D.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
-
E.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:19 p.m.