Triple
T5681567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium-3 |
E125209
|
entity |
| Predicate | meltingPointAt1atm |
P19716
|
FINISHED |
| Object | 0.3 K (approximate, under pressure) |
—
|
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: 0.3 K (approximate, under pressure) | Statement: [helium-3, meltingPointAt1atm, 0.3 K (approximate, under pressure)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meltingPointAt1atm Context triple: [helium-3, meltingPointAt1atm, 0.3 K (approximate, under pressure)]
-
A.
meltingPoint
chosen
Indicates the temperature at which a substance changes from solid to liquid under specified conditions.
-
B.
boilingPoint
Indicates the temperature at which a substance changes from liquid to gas under specified pressure conditions.
-
C.
physicalStateAtRoomTemperature
Indicates the physical state or phase (solid, liquid, gas, etc.) that an entity has when it is at standard room temperature.
-
D.
hasMeltingMechanism
Indicates that an entity possesses a specific mechanism or process by which it melts or causes melting.
-
E.
materialMelted
Indicates that a material has undergone melting, transitioning from a solid to a liquid state.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.