Triple
T3921319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi theory of beta decay |
E88964
|
entity |
| Predicate | breaksDownAt |
P14242
|
FINISHED |
| Object | high energies |
—
|
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: high energies | Statement: [Fermi theory of beta decay, breaksDownAt, high energies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksDownAt Context triple: [Fermi theory of beta decay, breaksDownAt, high energies]
-
A.
breaksDownWhen
chosen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
B.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
C.
breakdownLedTo
Indicates that one event or situation of breakdown caused or directly resulted in another event or outcome.
-
D.
associatedBreak
Indicates a relationship where one entity is linked to a specific break, interruption, or pause that is relevant to its state, schedule, or operation.
-
E.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.