Triple
T4574500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curie point |
E123110
|
entity |
| Predicate | definesTransitionBetween |
P49207
|
FINISHED |
| Object | ferromagnetic 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: ferromagnetic phase | Statement: [Curie point, definesTransitionBetween, ferromagnetic phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesTransitionBetween Context triple: [Curie point, definesTransitionBetween, ferromagnetic phase]
-
A.
isTransitionalBetween
Indicates that something serves as an intermediate or bridging state, form, or phase between two other distinct states, forms, or phases.
-
B.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
C.
linkedBenchmarkTransition
chosen
Indicates a transition or change that is directly associated with, or triggered by, a specific benchmark or reference point.
-
D.
dstTransitionRuleType
Indicates the type or category of rule that governs how a system transitions into or out of daylight saving time.
-
E.
transitionMechanismUsedWith
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c9f0bc81908d87f01ab067818a |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.