Triple
T36228512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eutelsat OneWeb |
E891174
|
entity |
| Predicate | hasSatelliteBand |
P126442
|
FINISHED |
| Object | Ku-band |
—
|
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: Ku-band | Statement: [Eutelsat OneWeb, hasSatelliteBand, Ku-band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSatelliteBand Context triple: [Eutelsat OneWeb, hasSatelliteBand, Ku-band]
-
A.
satelliteBand
chosen
Indicates that something operates in, uses, or is associated with a specific frequency band within the satellite communication spectrum.
-
B.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
-
C.
hasSatelliteConstellation
Indicates that an entity possesses or operates a specific group of satellites functioning together as a coordinated constellation.
-
D.
hasSatelliteStatus
Indicates that one entity holds the status of being a satellite (e.g., dependent, subordinate, or orbiting body) in relation to another entity.
-
E.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.