Triple
T22400761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 262 |
E553750
|
entity |
| Predicate | hasGasTemperature |
P100818
|
FINISHED |
| Object | cooler core gas compared to outer regions |
—
|
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: cooler core gas compared to outer regions | Statement: [Abell 262, hasGasTemperature, cooler core gas compared to outer regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGasTemperature Context triple: [Abell 262, hasGasTemperature, cooler core gas compared to outer regions]
-
A.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
exhaustGasTemperature
Indicates the temperature of the exhaust gases produced by an engine or combustion process.
-
C.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
D.
containsHotGas
Indicates that one entity encloses or holds within it a quantity or region of hot gas.
-
E.
hasTemperatureCategory
chosen
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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b39c908190a735aa860d733869 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.