Triple
T14990873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDF |
E373830
|
entity |
| Predicate | runIIEnergy |
P23068
|
FINISHED |
| Object | 1.96 TeV center-of-mass energy |
—
|
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: 1.96 TeV center-of-mass energy | Statement: [CDF, runIIEnergy, 1.96 TeV center-of-mass energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runIIEnergy Context triple: [CDF, runIIEnergy, 1.96 TeV center-of-mass energy]
-
A.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
B.
outputEnergy
Indicates that an entity produces or releases a certain amount or form of energy as a result of its operation or behavior.
-
C.
energyRegime
chosen
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
D.
hasEnergyManagement
Indicates that an entity possesses or is associated with a system, capability, or function for monitoring, controlling, or optimizing energy use.
-
E.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded715db408190b44e8a8452c79764 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.