Triple

T32807868
Position Surface form Disambiguated ID Type / Status
Subject DE000BASF111 E839064 entity
Predicate isRegulatedMarketSecurity P175139 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: [DE000BASF111, isRegulatedMarketSecurity, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRegulatedMarketSecurity
Context triple: [DE000BASF111, isRegulatedMarketSecurity, true]
  • A. isRegulatedMarket
    Indicates that a market operates under formal legal or regulatory oversight and must comply with specific rules and standards set by an authority.
  • B. isSoleSecuritiesMarketOf
    Indicates that one securities market is the only market on which a given security or set of securities is traded.
  • C. isEquitySecurity
    Indicates that the related financial instrument represents an ownership interest (equity) in an entity, rather than a debt or derivative claim.
  • D. 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.
  • E. hasRegulatoryMarket
    Indicates that an entity is subject to, or operates within, a specific regulatory framework or market oversight regime.
  • 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_69f3493d35208190b4351b4e85f2fa16 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6cee547108190ad3bc84297d8f516 completed May 3, 2026, 4:28 a.m.
PD Predicate disambiguation batch_69f6cc1667a48190b42684f6ec22dae9 completed May 3, 2026, 4:16 a.m.
PDg Predicate description generation batch_69f6ce6c76bc8190b865343d3f5810c9 completed May 3, 2026, 4:26 a.m.
Created at: May 1, 2026, 1:15 a.m.