Triple
T26981243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celsius |
E679604
|
entity |
| Predicate | offsetFromKelvin |
P161410
|
FINISHED |
| Object | 273.15 |
—
|
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: 273.15 | Statement: [Celsius, offsetFromKelvin, 273.15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetFromKelvin Context triple: [Celsius, offsetFromKelvin, 273.15]
-
A.
offsetFromFahrenheit
Indicates the numerical difference between a given temperature value and its equivalent expressed in degrees Fahrenheit.
-
B.
offsetFrom
Indicates that one entity is positioned or scheduled at a specific distance, time, or value away from another reference entity.
-
C.
offsetFromUTC
Indicates the time difference between a given time value and Coordinated Universal Time (UTC), typically expressed as an offset in hours and/or minutes.
-
D.
scaleZeroApproximateCelsiusEquivalent
Indicates that one scale’s zero point approximately corresponds to the temperature defined as zero degrees on the Celsius scale.
-
E.
offsetFromKoreaStandardTime
Indicates the time difference between a given time reference and Korea Standard Time (KST), typically expressed as an offset in hours or minutes.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621565a3c8190ba5ede5ab86328af |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:46 a.m.