Triple
T23487000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSS-14 |
E570560
|
entity |
| Predicate | designedToOperateAt |
P25150
|
FINISHED |
| Object | S-band frequencies |
—
|
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: S-band frequencies | Statement: [DSS-14, designedToOperateAt, S-band frequencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToOperateAt Context triple: [DSS-14, designedToOperateAt, S-band frequencies]
-
A.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
B.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
C.
operatingCondition
Indicates the specific state, requirements, or circumstances under which an entity functions or is intended to be used.
-
D.
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.
-
E.
operatesBelow
Indicates that one entity functions, acts, or is positioned at a lower level, layer, or hierarchy relative to 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a754825481909b005ca5654c3159 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.