Triple
T20778016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 1060 |
E511402
|
entity |
| Predicate | hasCoolingCore |
P141486
|
FINISHED |
| Object | weak or absent cooling core |
—
|
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: weak or absent cooling core | Statement: [Abell 1060, hasCoolingCore, weak or absent cooling core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoolingCore Context triple: [Abell 1060, hasCoolingCore, weak or absent cooling core]
-
A.
hasCoolingFlow
Indicates that an entity is equipped with or utilizes a system or mechanism to remove heat or maintain a lower temperature through the flow of a cooling medium.
-
B.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
-
C.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
-
D.
hasCoolingTunnels
Indicates that something is equipped with or contains tunnels specifically used for cooling purposes.
-
E.
coolingMethod
Indicates the technique or process used to remove heat from something or keep it at a lower temperature.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.