Triple
T478706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago Stock Exchange |
E9117
|
entity |
| Predicate | isMajorExchangeFor |
P6939
|
FINISHED |
| Object | Chilean companies |
—
|
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: Chilean companies | Statement: [Santiago Stock Exchange, isMajorExchangeFor, Chilean companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorExchangeFor Context triple: [Santiago Stock Exchange, isMajorExchangeFor, Chilean companies]
-
A.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
B.
isMostTradedCurrency
Indicates that a currency is the one with the highest trading volume or frequency in a given market or context.
-
C.
tradedOn
chosen
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
D.
hasMajorMarket
Indicates that an entity has a primary or most significant market in a specified location or segment.
-
E.
isMajorInternationalGatewayFor
Indicates that one entity serves as a primary, globally significant access point or hub for another entity’s international connections or flows.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.