Triple
T28533488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Positioning System satellites |
E722101
|
entity |
| Predicate | minimumOperationalConstellationSize |
P25780
|
FINISHED |
| Object | 24 |
—
|
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: 24 | Statement: [Global Positioning System satellites, minimumOperationalConstellationSize, 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumOperationalConstellationSize Context triple: [Global Positioning System satellites, minimumOperationalConstellationSize, 24]
-
A.
minimumOperationalSatellites
chosen
Indicates the smallest number of satellites required for a system or mission to function at its intended operational capacity.
-
B.
plannedConstellationSize
Indicates the intended total number of units or elements that are planned to be included in a constellation.
-
C.
numberOfSatellites
Indicates the quantity of satellites that are associated with or orbit a given entity.
-
D.
hasSatelliteConstellation
Indicates that an entity possesses or operates a specific group of satellites functioning together as a coordinated constellation.
-
E.
numberOfOrbitalPlanes
Indicates the specific count of distinct orbital planes associated with an object or system.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 3:30 a.m.