Triple
T9744677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COBE Differential Microwave Radiometer |
E236276
|
entity |
| Predicate | numberOfFrequencyBands |
P90465
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [COBE Differential Microwave Radiometer, numberOfFrequencyBands, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfFrequencyBands Context triple: [COBE Differential Microwave Radiometer, numberOfFrequencyBands, 3]
-
A.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
C.
hasNumberOfFMChannels
Indicates the relationship that specifies how many FM (frequency modulation) channels are associated with or supported by an entity.
-
D.
numberOfFullRangeChannels
Indicates the total count of channels that operate over the complete available range of values or frequencies.
-
E.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2f8e648190ad94c940f9dc1de0 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:23 p.m.