Triple

T29388621
Position Surface form Disambiguated ID Type / Status
Subject Associate E745316 entity
Predicate hasCostLevel P146877 FINISHED
Object lower than higher Bluetooth SIG membership tiers 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: lower than higher Bluetooth SIG membership tiers | Statement: [Associate, hasCostLevel, lower than higher Bluetooth SIG membership tiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCostLevel
Context triple: [Associate, hasCostLevel, lower than higher Bluetooth SIG membership tiers]
  • A. hasCost
    Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
  • B. listingCostLevel chosen
    Indicates the relative price range or expense level associated with a particular listing.
  • C. increasedCostFor
    Indicates that one entity causes or experiences a rise in the cost associated with another entity or activity.
  • D. hasUsageLevel
    Indicates the degree or intensity with which something is used or utilized.
  • E. hasConditionalityLevel
    Indicates that one entity is associated with a specific degree or level of conditional requirements, constraints, or dependencies relative to another entity or context.
  • 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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_6a0061454944819088a0babfe60f69fc completed May 10, 2026, 10:43 a.m.
PD Predicate disambiguation batch_6a0060b9ee108190b91e8d99a16f2b30 completed May 10, 2026, 10:40 a.m.
Created at: April 28, 2026, 2:40 p.m.