Triple
T12362650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/WAVES |
E294778
|
entity |
| Predicate | observationalDomain |
P104773
|
FINISHED |
| Object | radio frequency |
—
|
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: radio frequency | Statement: [S/WAVES, observationalDomain, radio frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationalDomain Context triple: [S/WAVES, observationalDomain, radio frequency]
-
A.
observationalCategory
Indicates that one entity classifies or groups another entity based on the type or category of observation it represents.
-
B.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
C.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
D.
observationalProperty
Indicates a characteristic or attribute of an entity that can be observed or measured, typically used to describe how it appears or behaves under observation.
-
E.
observationalStatus
Indicates the current state or condition of an observation, such as whether it has been made, recorded, verified, or remains pending.
- F. None of above. chosen
Provenance (4 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d9429ff2bc8190b09adf8f57fad451 |
completed | April 10, 2026, 6:34 p.m. |
Created at: April 8, 2026, 9:54 p.m.