Triple
T24692119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberhof bobsleigh, luge and skeleton track |
E611468
|
entity |
| Predicate | refrigerated |
P156995
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Oberhof bobsleigh, luge and skeleton track, refrigerated, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refrigerated Context triple: [Oberhof bobsleigh, luge and skeleton track, refrigerated, yes]
-
A.
isRefrigeratedForSale
Indicates that an item is kept under refrigeration specifically for the purpose of being offered for sale.
-
B.
refrigerationRequirement
Indicates that the related item or substance must be kept at a specified refrigerated temperature or storage condition.
-
C.
cryogen
Indicates that an entity is preserved or maintained at extremely low temperatures, typically to halt biological or chemical processes.
-
D.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
-
E.
isCryogenic
Indicates that something operates at, is designed for, or involves extremely low (cryogenic) temperatures.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 3:20 a.m.