Triple
T10038183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inertial Upper Stage |
E205225
|
entity |
| Predicate | hasGuidanceSystem |
P35891
|
FINISHED |
| Object | inertial guidance system |
—
|
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: inertial guidance system | Statement: [Inertial Upper Stage, hasGuidanceSystem, inertial guidance system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuidanceSystem Context triple: [Inertial Upper Stage, hasGuidanceSystem, inertial guidance system]
-
A.
primaryGuidanceSystem
Indicates that one entity functions as the main or principal guidance or navigation system for another entity.
-
B.
guidanceControl
Indicates that one entity directs, manages, or influences the behavior or decisions of another through guidance or control.
-
C.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
D.
hasNavigationTechnology
chosen
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
E.
hasSteering
Indicates that one entity is equipped with or possesses a steering mechanism that allows control of its direction.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee04afc8190904704d66e23a432 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.