Triple

T16062424
Position Surface form Disambiguated ID Type / Status
Subject T E389643 entity
Predicate underlyingCompanyISIN P6091 FINISHED
Object US00206R1023 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: US00206R1023 | Statement: [T, underlyingCompanyISIN, US00206R1023]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyISIN
Context triple: [T, underlyingCompanyISIN, US00206R1023]
  • A. parentCompanyISIN
    Indicates that the subject entity is associated with a parent company identified by the given ISIN (International Securities Identification Number).
  • B. associatedCompanyISINCountryCode
    Indicates that the relationship links a company to the country code corresponding to the ISIN of an associated company.
  • C. underlyingCompanyExchange
    Indicates that one entity is the stock exchange on which the underlying company of another financial instrument or contract is listed or traded.
  • D. ISIN chosen
    Indicates that an entity is identified or associated with a specific International Securities Identification Number (ISIN).
  • E. underlyingCompany
    Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
  • 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_69d86dae698881908327ef2d67706cb9 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1858a00888190b8505071575dc56f completed April 17, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e18272f2288190a17d45fb01cc2b07 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 4:57 a.m.