Triple
T3488119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ideal gas law |
E73657
|
entity |
| Predicate | temperatureUnit |
P12631
|
FINISHED |
| Object | kelvin |
—
|
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: kelvin | Statement: [ideal gas law, temperatureUnit, kelvin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureUnit Context triple: [ideal gas law, temperatureUnit, kelvin]
-
A.
typicalTemperatureScale
Indicates the temperature scale (such as Celsius or Fahrenheit) that is normally used to express temperature values for the given entity or context.
-
B.
symbolOfTemperature
Indicates that one entity serves as a symbolic representation or notation used to express the temperature of another entity.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
unitSystem
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
-
E.
unitOfMeasure
chosen
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9193688190aa0cbf87a7b99446 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.