Triple
T478700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago Stock Exchange |
E9117
|
entity |
| Predicate | hasMarketType |
P2821
|
FINISHED |
| Object | securities market |
—
|
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: securities market | Statement: [Santiago Stock Exchange, hasMarketType, securities market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketType Context triple: [Santiago Stock Exchange, hasMarketType, securities market]
-
A.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
B.
marketType
chosen
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
C.
hasMarketMakers
Indicates that an entity is associated with one or more market makers who provide liquidity or facilitate trading for it.
-
D.
hasMarketParticipants
Indicates that a market or trading venue involves or is associated with specific participating entities (such as buyers, sellers, or intermediaries).
-
E.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
- 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.