Triple
T36487141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta 3910 |
E898962
|
entity |
| Predicate | launchConfigurationCode |
P143661
|
FINISHED |
| Object | 3-9-1-0 |
—
|
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: 3-9-1-0 | Statement: [Delta 3910, launchConfigurationCode, 3-9-1-0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchConfigurationCode Context triple: [Delta 3910, launchConfigurationCode, 3-9-1-0]
-
A.
plannedLaunchConfiguration
Indicates that there is a specified configuration or setup intended to be used for a future launch event or operation.
-
B.
configurationCode
chosen
Indicates that an entity is associated with a specific configuration identifier or code that defines its setup or settings.
-
C.
launchDestination
Indicates the target location or endpoint toward which something is launched or sent.
-
D.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
E.
launchProfile
Indicates initiating or configuring the conditions, parameters, or settings under which a launch or execution process is carried out.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.