Triple
T31275896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBAS-1 |
E797513
|
entity |
| Predicate | deploymentOrbit |
P171533
|
FINISHED |
| Object | near-equatorial geostationary orbit |
—
|
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: near-equatorial geostationary orbit | Statement: [CBAS-1, deploymentOrbit, near-equatorial geostationary orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentOrbit Context triple: [CBAS-1, deploymentOrbit, near-equatorial geostationary orbit]
-
A.
relaunchOrbit
Indicates that an entity is placed back into orbit after having previously left or ceased its orbital path.
-
B.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
C.
deploymentBasis
Indicates the foundational rationale, conditions, or criteria on which a deployment is planned, justified, or carried out.
-
D.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
E.
spaceDependence
Indicates a relationship where one entity’s properties, behavior, or validity depend on spatial position or configuration relative to another entity or reference frame.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:13 p.m.