Triple
T1144082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XAMS |
E23522
|
entity |
| Predicate | isRegulatedMarket |
P24413
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [XAMS, isRegulatedMarket, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegulatedMarket Context triple: [XAMS, isRegulatedMarket, true]
-
A.
isPrimarySecuritiesMarketOf
Indicates that a market serves as the main or principal venue where a particular entity’s securities are initially issued, listed, or predominantly traded.
-
B.
regulatedMarketFor
Indicates that one entity functions as a regulated market or trading venue specifically for the financial instruments, assets, or products associated with another entity.
-
C.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
-
D.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
E.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc5008d8819095c1ffb5db5b4911 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bbb9fb4c81909dd39c496893c21b |
completed | March 1, 2026, 10:20 p.m. |
Created at: March 1, 2026, 7:44 p.m.