Triple
T14387861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fahrenheit |
E356770
|
entity |
| Predicate | conversionToCelsiusFormula |
P65804
|
FINISHED |
| Object | C = (F − 32) × 5⁄9 |
—
|
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: C = (F − 32) × 5⁄9 | Statement: [Fahrenheit, conversionToCelsiusFormula, C = (F − 32) × 5⁄9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToCelsiusFormula Context triple: [Fahrenheit, conversionToCelsiusFormula, C = (F − 32) × 5⁄9]
-
A.
offsetFromFahrenheit
Indicates the numerical difference between a given temperature value and its equivalent expressed in degrees Fahrenheit.
-
B.
absoluteZeroInCelsius
Indicates that the temperature value is equal to absolute zero when expressed in degrees Celsius.
-
C.
conversionUse
chosen
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
D.
conversionProgram
Indicates a program or process that transforms something from one form, state, or type into another.
-
E.
absoluteZeroInFahrenheit
Indicates that a given temperature value is equal to absolute zero when expressed in degrees Fahrenheit.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90283b9c8190b50d30ad58bfe085 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.