Triple
T15852799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTA |
E384380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulated market segment |
C14021
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regulated market segment Context triple: [MTA, instanceOf, regulated market segment]
-
A.
regulated market
chosen
A regulated market is an economic system in which the buying and selling of goods, services, or financial instruments operate under rules and oversight imposed by a governing authority to ensure fairness, stability, and compliance with legal standards.
-
B.
stock market segment
A stock market segment is a distinct subset of the overall stock market grouped by shared characteristics such as company size, industry, geography, or trading venue to facilitate targeted analysis and investment.
-
C.
regulated entity
A regulated entity is an organization or individual whose activities are subject to oversight, rules, and enforcement by a governmental or regulatory authority.
-
D.
self-regulatory organization
A self-regulatory organization is an entity, typically within a specific industry or profession, that creates and enforces rules and standards for its members to promote fair, ethical, and orderly conduct, often under the oversight of a governmental authority.
-
E.
market segment of the London Stock Exchange
A market segment of the London Stock Exchange is a defined subdivision of the exchange that groups securities with similar characteristics, regulatory requirements, and trading rules to facilitate organized listing and trading.
- F. None of above.
Provenance (1 batch)
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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.