Triple
T28533316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron Proton Alpha Monitor |
E722097
|
entity |
| Predicate | measuresParticleType |
P3639
|
FINISHED |
| Object | 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: electrons | Statement: [Electron Proton Alpha Monitor, measuresParticleType, electrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measuresParticleType Context triple: [Electron Proton Alpha Monitor, measuresParticleType, electrons]
-
A.
hasParticleType
chosen
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
B.
dominantParticleType
Indicates that one particle type is the primary or most prevalent component within a given system, context, or interaction.
-
C.
treatsParticlesAs
Indicates that one entity handles, models, or regards certain elements or components specifically as particles within a given context or system.
-
D.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
E.
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.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd737d08190be7abf4158f36d36 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:30 a.m.