Triple
T11692985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raptor engine |
E277914
|
entity |
| Predicate | guidanceIntegration |
P101298
|
FINISHED |
| Object | integrated with Starship flight control systems |
—
|
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: integrated with Starship flight control systems | Statement: [Raptor engine, guidanceIntegration, integrated with Starship flight control systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceIntegration Context triple: [Raptor engine, guidanceIntegration, integrated with Starship flight control systems]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
guidanceLocation
Indicates the place or spatial context where guidance, direction, or instructional support is provided or intended to occur.
-
D.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
E.
hasGuides
Indicates that an entity is associated with one or more guides that provide direction, instruction, or assistance.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47b9eb48190976a35e91e25b56b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.