Triple
T7188600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kelvin |
E167630
|
entity |
| Predicate | offsetFromCelsius |
P15747
|
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: [kelvin, offsetFromCelsius, +273.15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetFromCelsius Context triple: [kelvin, offsetFromCelsius, +273.15]
-
A.
offsetFrom
Indicates that one entity is positioned or scheduled at a specific distance, time, or value away from another reference entity.
-
B.
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.
-
C.
temperatureRangeDifference
Indicates the difference between two temperature ranges, typically measuring how much one range is higher or lower than another.
-
D.
isOffsetFrom
chosen
Indicates that one entity’s position, value, or occurrence is displaced by a specified amount or direction relative to another entity.
-
E.
temperatureProportionalTo
Indicates that the temperature of one entity changes in direct proportion to the temperature of another entity.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.