Triple
T37566240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ku-band |
E933962
|
entity |
| Predicate | hasPolarizationOptions |
P38744
|
FINISHED |
| Object | linear polarization |
—
|
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: linear polarization | Statement: [Ku-band, hasPolarizationOptions, linear polarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolarizationOptions Context triple: [Ku-band, hasPolarizationOptions, linear polarization]
-
A.
polarizationModes
chosen
Indicates the specific polarization states or configurations associated with a signal, wave, or optical/electromagnetic system.
-
B.
hasPolarSetting
Indicates that something is configured or oriented according to a polar coordinate or polar reference system.
-
C.
hasPolarCoverage
Indicates that an entity includes or provides coverage, presence, or applicability in polar regions.
-
D.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
E.
hasOpticalFeature
Indicates that an entity possesses a specific optical characteristic or component, such as a visual property, element, or feature related to light or vision.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.