Triple
T2139083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RADARSAT Constellation Mission |
E46719
|
entity |
| Predicate | numberOfSatellites |
P37023
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [RADARSAT Constellation Mission, numberOfSatellites, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSatellites Context triple: [RADARSAT Constellation Mission, numberOfSatellites, 3]
-
A.
minimumOperationalSatellites
Indicates the smallest number of satellites required for a system or mission to function at its intended operational capacity.
-
B.
numberOfOrbitalPlanes
Indicates the specific count of distinct orbital planes associated with an object or system.
-
C.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
D.
typeOfSatelliteOperated
Indicates that one entity operates or manages a satellite of a specified type or category in relation to another entity.
-
E.
numberOfAntennasPlanned
Indicates the planned or intended count of antennas associated with an entity or installation.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf71edf08190add69022aabfd49d |
completed | March 7, 2026, 6:02 a.m. |
Created at: March 4, 2026, 7:44 p.m.