Triple
T27626530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Investment Bank |
E696222
|
entity |
| Predicate | usesTradingVenues |
P170380
|
FINISHED |
| Object | global stock exchanges |
—
|
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: global stock exchanges | Statement: [Investment Bank, usesTradingVenues, global stock exchanges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTradingVenues Context triple: [Investment Bank, usesTradingVenues, global stock exchanges]
-
A.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
B.
hasTradingVenueCode
Indicates that an entity is associated with a specific trading venue through its designated code.
-
C.
identifiesTradingVenue
Indicates that one entity specifies or designates the trading venue associated with another entity or transaction.
-
D.
usesTradingSystem
Indicates that one entity employs or operates a particular trading system to conduct its trading activities.
-
E.
isElectronicTradingVenue
Indicates that one entity functions as a platform or venue where trading activities are conducted electronically rather than through traditional physical or manual means.
- F. None of above. chosen
Provenance (4 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 2:18 p.m.