Triple

T25859210
Position Surface form Disambiguated ID Type / Status
Subject BICEP experiments E651435 entity
Predicate frequencyCoverageIncludes P53436 FINISHED
Object 270 GHz 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: 270 GHz | Statement: [BICEP experiments, frequencyCoverageIncludes, 270 GHz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: frequencyCoverageIncludes
Context triple: [BICEP experiments, frequencyCoverageIncludes, 270 GHz]
  • A. hasFrequencyCoverage chosen
    Indicates that one entity provides, supports, or is applicable across a specified range or set of frequencies associated with another entity.
  • B. isFrequentlyCovered
    Indicates that an entity is regularly or commonly reported on, discussed, or featured, especially in media or informational sources.
  • C. isFrequentlyCoveredSince
    Indicates that one entity has been regularly or repeatedly covered (e.g., in media, reports, or discussions) starting from a specified point in time.
  • D. frequencyBandSupported
    Indicates that an entity supports operation or functionality within a specified frequency band.
  • E. isFrequentlyCoveredBy
    Indicates that one entity is regularly or repeatedly reported on, discussed, or featured by another entity, such as a media outlet or information source.
  • 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_69e7ab3a199c81909227cb964cacfe24 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6135293908190809e255bf6334760 completed May 2, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69f611a72780819082f44e66ca2c6ac9 completed May 2, 2026, 3 p.m.
Created at: April 22, 2026, 8:04 a.m.