Triple
T27674019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSLC |
E697732
|
entity |
| Predicate | launchAzimuthSpecialization |
P21241
|
FINISHED |
| Object | high-inclination orbits |
—
|
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: high-inclination orbits | Statement: [TSLC, launchAzimuthSpecialization, high-inclination orbits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAzimuthSpecialization Context triple: [TSLC, launchAzimuthSpecialization, high-inclination orbits]
-
A.
launchAzimuth
chosen
Indicates the directional angle or bearing along which a launch (such as a rocket or missile) is initiated relative to a reference direction.
-
B.
launchVehicleRole
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
-
C.
launchVehicleProvider
Indicates the entity that supplies or operates the launch vehicle used to carry a payload into space.
-
D.
launchesFromSilo
Indicates that something is launched starting from a silo as its point of origin.
-
E.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:42 p.m.