Triple

T1402213
Position Surface form Disambiguated ID Type / Status
Subject Nasdaq Biotechnology Index E31609 entity
Predicate hasRebalancingFrequency P7407 FINISHED
Object quarterly 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: quarterly | Statement: [Nasdaq Biotechnology Index, hasRebalancingFrequency, quarterly]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRebalancingFrequency
Context triple: [Nasdaq Biotechnology Index, hasRebalancingFrequency, quarterly]
  • A. hasRebalancing
    Indicates that an entity undergoes or is subject to an adjustment process to restore a desired balance or allocation among its components or related elements.
  • B. tienePeriodicidad chosen
    Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
  • C. hasCheckAndBalanceFunction
    Indicates that one entity performs a checking or limiting role on another entity’s powers, providing oversight and balance within a system.
  • D. performedFrequency
    Indicates how often an action or activity is carried out within a given time period.
  • E. hasCheckAndBalanceWith
    Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
  • 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_69a49918e1f88190ba610f9dc8114578 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c39ef554819096c17bca5891829b completed March 1, 2026, 10:54 p.m.
PD Predicate disambiguation batch_69a4bf030a388190bc82d30b9233e873 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:59 p.m.