Triple
T7188596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kelvin |
E167630
|
entity |
| Predicate | zeroPoint |
P65427
|
FINISHED |
| Object | absolute zero |
—
|
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: absolute zero | Statement: [kelvin, zeroPoint, absolute zero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zeroPoint Context triple: [kelvin, zeroPoint, absolute zero]
-
A.
zeroConcept
Indicates a conceptual or abstract entity that has no concrete instances or realizations in 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.
yearZero
Indicates that the referenced year is designated as the starting point (year 0) of a particular calendar, timeline, or counting system.
-
E.
digitSymbolForZero
Indicates that something serves as the written digit symbol representing the numerical value zero.
- 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.