Triple
T27528774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VERITAS |
E694910
|
entity |
| Predicate | sensitivityRange |
P24994
|
FINISHED |
| Object | very high energy (VHE) gamma rays |
—
|
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: very high energy (VHE) gamma rays | Statement: [VERITAS, sensitivityRange, very high energy (VHE) gamma rays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensitivityRange Context triple: [VERITAS, sensitivityRange, very high energy (VHE) gamma rays]
-
A.
sensitivityRegion
Indicates the specific area or domain within which a subject is particularly responsive, vulnerable, or reactive to a given influence or condition.
-
B.
sensitivityFeature
chosen
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
C.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
D.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
E.
abilityRange
Indicates the spatial or contextual extent within which an entity’s ability, power, or effect can be applied or is valid.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f31e12c8190880b758fef6a07e0 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:25 p.m.