Triple
T380029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi surface |
E8657
|
entity |
| Predicate | temperatureCondition |
P2900
|
FINISHED |
| Object | zero temperature |
—
|
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: zero temperature | Statement: [Fermi surface, temperatureCondition, zero temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureCondition Context triple: [Fermi surface, temperatureCondition, zero temperature]
-
A.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
environmentalCondition
chosen
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
C.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
D.
averageTemperature
Indicates the typical or mean temperature value associated with an entity over a specified period or context.
-
E.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.