Triple
T13912954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landau–Pomeranchuk–Migdal effect |
E334544
|
entity |
| Predicate | affectsProcess |
P112258
|
FINISHED |
| Object | bremsstrahlung |
—
|
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: bremsstrahlung | Statement: [Landau–Pomeranchuk–Migdal effect, affectsProcess, bremsstrahlung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsProcess Context triple: [Landau–Pomeranchuk–Migdal effect, affectsProcess, bremsstrahlung]
-
A.
affectsProgram
Indicates that one entity produces an influence or change on a program, altering its behavior, state, or outcome.
-
B.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
C.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
D.
affectedByProject
Indicates that an entity experiences an impact, change, or influence as a result of a specific project.
-
E.
affectedProvision
Indicates that a particular legal provision is impacted, modified, or influenced by another action, decision, or provision.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.