Triple
T17105288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kramers degeneracy |
E415082
|
entity |
| Predicate | brokenBy |
P125945
|
FINISHED |
| Object | magnetic fields |
—
|
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: magnetic fields | Statement: [Kramers degeneracy, brokenBy, magnetic fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokenBy Context triple: [Kramers degeneracy, brokenBy, magnetic fields]
-
A.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
B.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
C.
broke
Indicates that one entity caused another entity to separate into pieces or cease functioning, typically through force or damage.
-
D.
brokenUpAt
Indicates that a romantic or close relationship between two entities ended at a specific time or date.
-
E.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
- F. None of above. chosen
Provenance (4 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2683fc81908af2df9012addecb |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.