Triple
T27638488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcor Life Extension Foundation |
E696526
|
entity |
| Predicate | storesAtTemperature |
P4459
|
FINISHED |
| Object | approximately −196 °C |
—
|
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: approximately −196 °C | Statement: [Alcor Life Extension Foundation, storesAtTemperature, approximately −196 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesAtTemperature Context triple: [Alcor Life Extension Foundation, storesAtTemperature, approximately −196 °C]
-
A.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
B.
isRefrigeratedForSale
Indicates that an item is kept under refrigeration specifically for the purpose of being offered for sale.
-
C.
refrigerated
Indicates that something is kept at a low temperature, typically in a refrigerator, to preserve its condition or freshness.
-
D.
hasTemperatureRegime
Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
-
E.
hasTemperature
chosen
Indicates that an entity possesses or is characterized by a specific temperature value.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:25 p.m.