Triple
T230721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proton Synchrotron |
E4404
|
entity |
| Predicate | designedEnergy |
P3964
|
FINISHED |
| Object | 25 GeV |
—
|
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: 25 GeV | Statement: [Proton Synchrotron, designedEnergy, 25 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedEnergy Context triple: [Proton Synchrotron, designedEnergy, 25 GeV]
-
A.
designEnergy
chosen
Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
-
B.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
C.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
D.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified by another entity.
-
E.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.