Triple

T22503346
Position Surface form Disambiguated ID Type / Status
Subject CAP E556329 entity
Predicate hasUnderlyingSector P148488 FINISHED
Object technology 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: technology | Statement: [CAP, hasUnderlyingSector, technology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingSector
Context triple: [CAP, hasUnderlyingSector, technology]
  • A. hasUnderlyingMarket
    Indicates that one entity is based on, derives its value from, or is traded with reference to another entity that serves as its fundamental market.
  • B. hasUnderlyingAssets
    Indicates that one entity is supported, backed, or derived from another entity or set of entities that serve as its foundational assets.
  • C. hasUnderlyingIssuer
    Indicates that one entity serves as the fundamental or primary issuer behind another entity, such as a financial instrument or structured product.
  • D. hasUnderlyingLEI
    Indicates that an entity is associated with, or identified by, a specific underlying Legal Entity Identifier (LEI).
  • E. underlyingAsset
    Indicates that one asset serves as the fundamental reference or basis for the value, performance, or contractual terms of another financial instrument or derivative.
  • 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d5a01888190ba65a05616b63cbe completed April 29, 2026, 1:22 a.m.
PD Predicate disambiguation batch_69e898be31448190be5ae7f5656f0497 completed April 22, 2026, 9:45 a.m.
PDg Predicate description generation batch_69e8aa3b4c288190951cca06d42bea51 completed April 22, 2026, 11 a.m.
Created at: April 16, 2026, 8:50 p.m.