Triple
T12601354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahsat |
E300864
|
entity |
| Predicate | orbitalCoverage |
P105647
|
FINISHED |
| Object | Ka-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: Ka-band | Statement: [Yahsat, orbitalCoverage, Ka-band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalCoverage Context triple: [Yahsat, orbitalCoverage, Ka-band]
-
A.
orbitsCovered
Indicates that one entity completes or spans a specified number of orbital revolutions around another entity.
-
B.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
C.
supportsOrbitRegimes
Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of another entity.
-
D.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
E.
hemisphereCoverageByImaging
Indicates the extent to which a particular hemisphere is covered or captured by an imaging procedure or dataset.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95590a5e08190842b988531cf2921 |
completed | April 10, 2026, 7:54 p.m. |
Created at: April 9, 2026, 5:09 p.m.