Triple

T36904229
Position Surface form Disambiguated ID Type / Status
Subject Motorola C157 E912725 entity
Predicate basebandType P186740 FINISHED
Object Calypso-based GSM baseband 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: Calypso-based GSM baseband | Statement: [Motorola C157, basebandType, Calypso-based GSM baseband]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: basebandType
Context triple: [Motorola C157, basebandType, Calypso-based GSM baseband]
  • A. usesBasebandTransmission
    Indicates that one entity employs baseband transmission, meaning it sends digital signals directly over a communication medium without modulating them onto a higher-frequency carrier.
  • B. baseType
    Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
  • C. bandwidthCharacteristic
    Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
  • D. transmissionBand
    Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
  • E. dataBusType
    Indicates the type or category of data bus used to transfer data between components or systems.
  • 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_69f76e879768819085c2fb31a6a5b44b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fa0a7b00948190a257273d9968c5d7 completed May 5, 2026, 3:19 p.m.
PD Predicate disambiguation batch_69f9fec9c9488190ae2a349651a02782 completed May 5, 2026, 2:29 p.m.
PDg Predicate description generation batch_69fa0a799b9081909bfa8293a22c4b00 completed May 5, 2026, 3:19 p.m.
Created at: May 3, 2026, 4:13 p.m.