Triple
T10846135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OneWeb satellites |
E256012
|
entity |
| Predicate | plannedConstellationSize |
P96039
|
FINISHED |
| Object | 648 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: 648 satellites | Statement: [OneWeb satellites, plannedConstellationSize, 648 satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedConstellationSize Context triple: [OneWeb satellites, plannedConstellationSize, 648 satellites]
-
A.
typicalConstellationSize
Indicates the usual or characteristic size associated with a given constellation.
-
B.
numberOfGEOSatellitesPlanned
Indicates the planned quantity of GEO (geostationary) satellites associated with a given entity or mission.
-
C.
numberOfAntennasPlanned
Indicates the planned or intended count of antennas associated with an entity or installation.
-
D.
numberOfConstellations
Indicates the total count of constellations associated with a given subject.
-
E.
numberOfStarsInConstellation
Indicates the numerical count of stars that belong to a given constellation.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:19 p.m.