Triple
T21989335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omni-Purpose Apparatus for LEP |
E543042
|
entity |
| Predicate | primaryBeamParticles |
P69515
|
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: [Omni-Purpose Apparatus for LEP, primaryBeamParticles, electrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBeamParticles Context triple: [Omni-Purpose Apparatus for LEP, primaryBeamParticles, electrons]
-
A.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
B.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
C.
usesPrimaryBeam
Indicates that one entity employs another entity as its main or principal beam in an operation or structure.
-
D.
beamComposition
chosen
Indicates the constituent particles, materials, or components that make up a given beam.
-
E.
beamProperty
Indicates that one entity is a physical or structural beam and the other specifies a characteristic or attribute of that beam.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.