Triple
T928443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Discovery |
E20037
|
entity |
| Predicate | auxiliaryPropulsion |
P21496
|
FINISHED |
| Object | two Solid Rocket Boosters |
—
|
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: two Solid Rocket Boosters | Statement: [Space Shuttle Discovery, auxiliaryPropulsion, two Solid Rocket Boosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auxiliaryPropulsion Context triple: [Space Shuttle Discovery, auxiliaryPropulsion, two Solid Rocket Boosters]
-
A.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
B.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
C.
propulsionCycle
Indicates the type or pattern of propulsion operation or cycle that characterizes how a system generates and sustains thrust or movement.
-
D.
assistedShip
Indicates that one entity helped or supported a ship in performing an operation, task, or journey.
-
E.
propulsionLayout
Indicates how propulsion components are arranged or configured relative to each other within a system.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b34775ac8190aabbd047a36cec6b |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b2f4e3fc81908c8a2d1fbef9c5d2 |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:40 p.m.