Triple
T22695694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILD detector concept |
E561165
|
entity |
| Predicate | energyRangeDesignedFor |
P1457
|
FINISHED |
| Object | center-of-mass energies from about 250 GeV to 1 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: center-of-mass energies from about 250 GeV to 1 TeV | Statement: [ILD detector concept, energyRangeDesignedFor, center-of-mass energies from about 250 GeV to 1 TeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRangeDesignedFor Context triple: [ILD detector concept, energyRangeDesignedFor, center-of-mass energies from about 250 GeV to 1 TeV]
-
A.
tierRange
Indicates that one entity specifies the minimum and maximum tier levels within which another entity falls or is applicable.
-
B.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
C.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
D.
categoryRange
Indicates that a category or classification spans from a defined lower bound to an upper bound within a specified range.
-
E.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789e05d88190b9d51bb3f8e3e9d4 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.