Triple
T23910409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSLV-I |
E601922
|
entity |
| Predicate | thirdLaunchOutcome |
P21238
|
FINISHED |
| Object | success |
—
|
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: success | Statement: [KSLV-I, thirdLaunchOutcome, success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdLaunchOutcome Context triple: [KSLV-I, thirdLaunchOutcome, success]
-
A.
launchOutcome
chosen
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
B.
secondGenerationLaunch
Indicates that an entity initiates or is associated with the launch of a second-generation version of a product, system, or technology.
-
C.
thirdCreationStatus
Indicates the status or outcome of a third instance or attempt of a creation process in relation to an entity.
-
D.
thirdCycle
Indicates that the related entity is in, associated with, or pertains to the third cycle or third iteration within a defined sequence, process, or phase.
-
E.
nextGenerationLaunch
Indicates the initiation or deployment of a subsequent, more advanced version of a product, system, or technology.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce94f65c8190807723344fa0b837 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:38 p.m.