Triple
T37030929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E916490
|
entity |
| Predicate | firstSuccessfulMissionName |
P205699
|
FINISHED |
| Object | Launch Demo 2 |
E205859
|
NE 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: Launch Demo 2 | Statement: [LauncherOne, firstSuccessfulMissionName, Launch Demo 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSuccessfulMissionName Context triple: [LauncherOne, firstSuccessfulMissionName, Launch Demo 2]
-
A.
firstMissionName
Indicates the name assigned to an entity’s first mission or initial operation.
-
B.
firstSuccessfulDemoMission
Indicates that the mission is the first demonstration mission that achieved its intended success.
-
C.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
D.
firstOperationalCargoMission
Indicates that the subject entity is the earliest or initial cargo mission to be put into operational service for the related program, system, or route.
-
E.
firstLaunchMission
Indicates that a mission is the first launch associated with a particular object, program, or entity.
- F. None of above. chosen
Provenance (5 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c35cd848190a25c5ecb6d69bcb2 |
completed | June 26, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.