Triple
T19688603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC |
E472775
|
entity |
| Predicate | usedPolarizedBeams |
P68962
|
FINISHED |
| Object | electron beam polarization |
—
|
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: electron beam polarization | Statement: [SLC, usedPolarizedBeams, electron beam polarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPolarizedBeams Context triple: [SLC, usedPolarizedBeams, electron beam polarization]
-
A.
electronBeamPolarization
chosen
Indicates the orientation and degree of alignment of the spins or directions of electrons within an electron beam.
-
B.
positronBeamPolarization
Indicates the degree and orientation of the spin alignment (polarization) of a beam of positrons in an experiment or system.
-
C.
polarizationModes
Indicates the specific polarization states or configurations associated with a signal, wave, or optical/electromagnetic system.
-
D.
usesPrimaryBeam
Indicates that one entity employs another entity as its main or principal beam in an operation or structure.
-
E.
hasPolarSetting
Indicates that something is configured or oriented according to a polar coordinate or polar reference system.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420e5b788190a63ff6b83383b0e8 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.