Triple
T13912956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landau–Pomeranchuk–Migdal effect |
E334544
|
entity |
| Predicate | affectsParticle |
P25489
|
FINISHED |
| Object | high-energy electrons |
—
|
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-energy electrons | Statement: [Landau–Pomeranchuk–Migdal effect, affectsParticle, high-energy electrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsParticle Context triple: [Landau–Pomeranchuk–Migdal effect, affectsParticle, high-energy electrons]
-
A.
usedParticle
Indicates that one entity employs or applies a particular particle (e.g., subatomic, linguistic, or material) in some process, context, or construction involving another entity.
-
B.
concernsParticle
Indicates that something is about or relates specifically to a particular particle or type of particle.
-
C.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
D.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
E.
affectsPhenomenon
Indicates that one phenomenon produces an influence or change on another phenomenon.
- 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_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. |
Created at: April 9, 2026, 10:16 p.m.