Triple
T24824748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PETRA |
E621156
|
entity |
| Predicate | beamConfiguration |
P133359
|
FINISHED |
| Object | counter-rotating electron and positron beams |
—
|
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: counter-rotating electron and positron beams | Statement: [PETRA, beamConfiguration, counter-rotating electron and positron beams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamConfiguration Context triple: [PETRA, beamConfiguration, counter-rotating electron and positron beams]
-
A.
beamUse
Indicates the action of directing or emitting a beam (such as light, energy, or signal) from one entity toward a target or in a specific direction.
-
B.
beamProperty
chosen
Indicates that one entity is a physical or structural beam and the other specifies a characteristic or attribute of that beam.
-
C.
beamComposition
Indicates the constituent particles, materials, or components that make up a given beam.
-
D.
detectorConfiguration
Indicates a relationship where a detector is associated with, or operates under, a specific configuration or set of parameter settings.
-
E.
beamName
Indicates that an entity has or is associated with a specific beam identifier or label.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:05 a.m.