Triple
T33797014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium LLC |
E866100
|
entity |
| Predicate | satelliteConstellationShape |
P153471
|
FINISHED |
| Object | polar orbit constellation |
—
|
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: polar orbit constellation | Statement: [Iridium LLC, satelliteConstellationShape, polar orbit constellation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satelliteConstellationShape Context triple: [Iridium LLC, satelliteConstellationShape, polar orbit constellation]
-
A.
hasSatelliteConstellation
chosen
Indicates that an entity possesses or operates a specific group of satellites functioning together as a coordinated constellation.
-
B.
constellationShape
Indicates that one entity has the outline, pattern, or visual form corresponding to a particular constellation.
-
C.
spacecraftShape
Indicates the geometric form or physical configuration that a spacecraft possesses.
-
D.
satelliteSystem
Indicates a relationship where one system functions as a satellite or subordinate system orbiting, supporting, or depending on another primary system.
-
E.
numberOfSatellites
Indicates the quantity of satellites that are associated with or orbit a given entity.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.