Triple
T24916372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HERA |
E623995
|
entity |
| Predicate | energyElectrons |
P122627
|
FINISHED |
| Object | about 27.5 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: about 27.5 GeV | Statement: [HERA, energyElectrons, about 27.5 GeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyElectrons Context triple: [HERA, energyElectrons, about 27.5 GeV]
-
A.
electronEnergy
chosen
Indicates the amount of energy associated with an electron in a given state, configuration, or context.
-
B.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
C.
energyPotential
Indicates a relationship where one entity possesses or confers the capacity to perform work or cause change (potential energy) relative to another entity or state.
-
D.
energy
Indicates that an entity possesses, produces, consumes, or is associated with a quantifiable amount or type of energy.
-
E.
energyDomain
Indicates that one entity operates within, belongs to, or is characterized by a particular type or domain of energy associated with the other entity.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4238c52488190a58b1191f4dc3373 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:28 a.m.