Triple
T3834140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSS Unity |
E91086
|
entity |
| Predicate | apogeeCapability |
P52280
|
FINISHED |
| Object | over 80 kilometers altitude |
—
|
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: over 80 kilometers altitude | Statement: [VSS Unity, apogeeCapability, over 80 kilometers altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apogeeCapability Context triple: [VSS Unity, apogeeCapability, over 80 kilometers altitude]
-
A.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
-
B.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
E.
seekerCapability
Indicates that an entity has the ability or function to detect, track, or locate a target or object.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:17 p.m.