Triple

T6111160
Position Surface form Disambiguated ID Type / Status
Subject Peierls transition E136241 entity
Predicate temperatureAtWhichOccurs P4459 FINISHED
Object Peierls transition temperature T_P 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: Peierls transition temperature T_P | Statement: [Peierls transition, temperatureAtWhichOccurs, Peierls transition temperature T_P]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: temperatureAtWhichOccurs
Context triple: [Peierls transition, temperatureAtWhichOccurs, Peierls transition temperature T_P]
  • A. typicalTemperature
    Indicates the usual or characteristic temperature associated with an entity under normal conditions.
  • B. hasTemperature chosen
    Indicates that an entity possesses or is characterized by a specific temperature value.
  • C. temperatureDependent
    Indicates that the existence, intensity, or outcome of a relationship or process varies as a function of temperature.
  • D. minSurfaceTemperature
    Indicates the lowest temperature value observed or allowed on the surface of an object or environment.
  • E. growthTemperatureRange
    Indicates the range of temperatures within which an organism or entity can grow or function effectively.
  • 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_69c0089ea6f88190b349be53e04b4f5f completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05bbbbea88190b889a7c30af1d71a completed March 22, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69c049f80e2081909b7d84a104cda68d completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:13 p.m.