Triple
T2633533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B3 – Brasil Bolsa Balcão |
E59689
|
entity |
| Predicate | clearsFor |
P35399
|
FINISHED |
| Object | equity markets |
—
|
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: equity markets | Statement: [B3 – Brasil Bolsa Balcão, clearsFor, equity markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clearsFor Context triple: [B3 – Brasil Bolsa Balcão, clearsFor, equity markets]
-
A.
clearingSystem
chosen
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
B.
clearingHouse
Indicates that an entity functions as an intermediary organization that receives, processes, and redistributes transactions, information, or obligations between other parties.
-
C.
clearanceRequired
Indicates that a specific level of authorization or security clearance is needed before the related action can be performed or access can be granted.
-
D.
clearanceBelow
Indicates that one entity is positioned at a lower vertical clearance level than another, typically with less space between it and an underlying reference surface.
-
E.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.