Triple
T2882442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Heavy booster |
E59426
|
entity |
| Predicate | launchSystemType |
P15304
|
FINISHED |
| Object | two-stage-to-orbit |
—
|
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-stage-to-orbit | Statement: [Super Heavy booster, launchSystemType, two-stage-to-orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSystemType Context triple: [Super Heavy booster, launchSystemType, two-stage-to-orbit]
-
A.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
B.
launchPlatformName
Indicates the name of the platform or site from which a launch (typically of a vehicle, rocket, or mission) is conducted.
-
C.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
D.
systemType
chosen
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02aa5948190a2e0bd9168232bd5 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.