Triple
T4461495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner crystal |
E98264
|
entity |
| Predicate | hasPhaseTransitionType |
P51172
|
FINISHED |
| Object | quantum phase transition |
—
|
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: quantum phase transition | Statement: [Wigner crystal, hasPhaseTransitionType, quantum phase transition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhaseTransitionType Context triple: [Wigner crystal, hasPhaseTransitionType, quantum phase transition]
-
A.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
-
B.
hasWarmPhase
Indicates that an entity undergoes or includes a period characterized by relatively higher temperatures or warmer conditions.
-
C.
hasMultiplePhases
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
D.
hasColdPhase
Indicates that an entity undergoes or includes a period or stage characterized by low temperature or cold conditions.
-
E.
phaseType
chosen
Indicates the specific stage or phase category that an associated process, event, or lifecycle instance belongs to.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35674f718819089388c3924dd1414 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.