Triple
T13377768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmic Background Explorer |
E319232
|
entity |
| Predicate | temperatureMeasured |
P4459
|
FINISHED |
| Object | 2.725 K |
—
|
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: 2.725 K | Statement: [Cosmic Background Explorer, temperatureMeasured, 2.725 K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureMeasured Context triple: [Cosmic Background Explorer, temperatureMeasured, 2.725 K]
-
A.
hasTemperature
chosen
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
temperatureConditions
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
C.
temperatureChange
Indicates a change in temperature between two states, times, or conditions, specifying how much and in which direction the temperature has varied.
-
D.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
E.
hasTemperatureCategory
Indicates that an entity is associated with a specific qualitative temperature classification (e.g., hot, cold, warm).
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.