Triple
T95251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linac4 |
E1915
|
entity |
| Predicate | energyRange |
P1457
|
FINISHED |
| Object | from 45 keV to 160 MeV |
—
|
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: from 45 keV to 160 MeV | Statement: [Linac4, energyRange, from 45 keV to 160 MeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyRange Context triple: [Linac4, energyRange, from 45 keV to 160 MeV]
-
A.
typicalEnergyRange
chosen
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
B.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
C.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
D.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
usesElectricityStandard
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by 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_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.