Triple
T9837683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus XL |
E239143
|
entity |
| Predicate | stagesConfiguration |
P7615
|
FINISHED |
| Object | three-stage solid rocket |
—
|
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: three-stage solid rocket | Statement: [Pegasus XL, stagesConfiguration, three-stage solid rocket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stagesConfiguration Context triple: [Pegasus XL, stagesConfiguration, three-stage solid rocket]
-
A.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
B.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
C.
numberOfStages
chosen
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
D.
setsStageFor
Indicates that one event, condition, or action creates the necessary circumstances or groundwork for another to occur.
-
E.
stage3Includes
Indicates that a process or workflow’s third stage contains, encompasses, or incorporates a specified component, step, or element.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.