Triple
T25475110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemOperationalRangeCategory |
P25150
|
FINISHED |
| Object | short range |
—
|
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: short range | Statement: [Grail, systemOperationalRangeCategory, short range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemOperationalRangeCategory Context triple: [Grail, systemOperationalRangeCategory, short range]
-
A.
operationalRange
chosen
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
B.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
C.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
D.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
E.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:25 p.m.