Triple
T27841713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dicke radiometer |
E703696
|
entity |
| Predicate | usedForDiscoveryOf |
P108551
|
FINISHED |
| Object | cosmic microwave background radiation |
—
|
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: cosmic microwave background radiation | Statement: [Dicke radiometer, usedForDiscoveryOf, cosmic microwave background radiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForDiscoveryOf Context triple: [Dicke radiometer, usedForDiscoveryOf, cosmic microwave background radiation]
-
A.
namedForDiscoveryOf
Indicates that one entity is named in recognition of another entity’s discovery of something.
-
B.
supportedDiscoveryOf
chosen
Indicates that one entity aided, enabled, or contributed to another entity’s act of discovering something.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
knownForDiscovering
Indicates that one entity is recognized or notable for having discovered another entity.
-
E.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 6:03 p.m.