Triple
T5767086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Area of SPS |
E127240
|
entity |
| Predicate | beamOperationMode |
P27468
|
FINISHED |
| Object | slow-extracted SPS 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: slow-extracted SPS beams | Statement: [North Area of SPS, beamOperationMode, slow-extracted SPS beams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beamOperationMode Context triple: [North Area of SPS, beamOperationMode, slow-extracted SPS 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.
instrumentMode
Indicates the manner, setting, or operational mode in which an instrument is used to perform an action or measurement.
-
C.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
-
D.
operationType
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
-
E.
modeType
chosen
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.