Triple
T18426560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XY model |
E450153
|
entity |
| Predicate | highTemperaturePhase |
P103042
|
FINISHED |
| Object | disordered phase |
—
|
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: disordered phase | Statement: [XY model, highTemperaturePhase, disordered phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highTemperaturePhase Context triple: [XY model, highTemperaturePhase, disordered phase]
-
A.
summerHighTemperaturesOftenExceed
Indicates that during the summer season, the high temperatures in a given location frequently surpass a specified threshold.
-
B.
maximumForGivenTemperatures
Indicates the maximum value attained when considering a specified set or range of temperatures.
-
C.
hasPhaseTransition
chosen
Indicates that an entity undergoes or exhibits a change from one physical phase or state of matter to another.
-
D.
maxSurfaceTemperature
Indicates the highest temperature that the surface of an entity can reach or sustain under specified conditions.
-
E.
hasCriticalTemperature
Indicates that an entity possesses a specific temperature value at which a critical physical change or phase transition occurs.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b13ee88819091e7e007d17dcc73 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:24 a.m.