Triple
T95175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Hadron Collider |
E1914
|
entity |
| Predicate | run1Energy |
P1457
|
FINISHED |
| Object | 7 to 8 TeV |
—
|
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: 7 to 8 TeV | Statement: [Large Hadron Collider, run1Energy, 7 to 8 TeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: run1Energy Context triple: [Large Hadron Collider, run1Energy, 7 to 8 TeV]
-
A.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
B.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
C.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
runnerUpBasedIn
Indicates that an entity serving as a runner-up is located in or associated with a particular place or base of operations.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.