Triple
T30877084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEHF military communications satellites |
E786506
|
entity |
| Predicate | constellationSizePlanned |
P96039
|
FINISHED |
| Object | 6 satellites |
—
|
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: 6 satellites | Statement: [AEHF military communications satellites, constellationSizePlanned, 6 satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constellationSizePlanned Context triple: [AEHF military communications satellites, constellationSizePlanned, 6 satellites]
-
A.
plannedConstellationSize
chosen
Indicates the intended total number of units or elements that are planned to be included in a constellation.
-
B.
typicalConstellationSize
Indicates the usual or characteristic size associated with a given constellation.
-
C.
isSmallConstellation
Indicates that the subject constellation is relatively small in size or area compared to typical constellations.
-
D.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
E.
constellationConfiguration
Indicates the specific spatial arrangement and relative positioning of elements within a constellation.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:48 p.m.