Triple
T30877115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUOS |
E786507
|
entity |
| Predicate | numberOfOnOrbitSpareSatellites |
P202712
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [MUOS, numberOfOnOrbitSpareSatellites, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfOnOrbitSpareSatellites Context triple: [MUOS, numberOfOnOrbitSpareSatellites, 1]
-
A.
plannedSpareSatellites
Indicates that additional satellites are intentionally scheduled or reserved as backups or replacements for primary satellites.
-
B.
numberOfSatellites
Indicates the quantity of satellites that are associated with or orbit a given entity.
-
C.
numberOfGEOSatellitesPlanned
Indicates the planned quantity of GEO (geostationary) satellites associated with a given entity or mission.
-
D.
minimumOperationalSatellites
Indicates the smallest number of satellites required for a system or mission to function at its intended operational capacity.
-
E.
numberOfGeostationarySatellites
Indicates the quantity of geostationary satellites associated with a given entity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00af6b3a948190a92813c13384c304 |
completed | May 10, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_6a00aec35610819085dd5137715a4228 |
completed | May 10, 2026, 4:13 p.m. |
| PDg | Predicate description generation | batch_6a00af6a5ffc819095c7331518a09f53 |
completed | May 10, 2026, 4:16 p.m. |
Created at: April 29, 2026, 8:48 p.m.