Triple
T26981235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celsius |
E679604
|
entity |
| Predicate | zeroPointDefinedBy |
P65427
|
FINISHED |
| Object | freezing point of water at 1 atm |
—
|
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: freezing point of water at 1 atm | Statement: [Celsius, zeroPointDefinedBy, freezing point of water at 1 atm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zeroPointDefinedBy Context triple: [Celsius, zeroPointDefinedBy, freezing point of water at 1 atm]
-
A.
zeroDefinition
Indicates that something has no defined value, quantity, or specification within the given context.
-
B.
formsZeroPointFor
chosen
Indicates that one entity serves as the reference or origin point (zero point) for measuring or defining another entity.
-
C.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
D.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
E.
hasZeroPosition
Indicates that an entity occupies or is assigned to the reference (zero) position within a defined coordinate system or ordered structure.
- 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_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. |
Created at: April 27, 2026, 6:46 a.m.