Triple
T7866788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn IB |
E182635
|
entity |
| Predicate | launchSuccessRate |
P7192
|
FINISHED |
| Object | 100 percent |
—
|
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: 100 percent | Statement: [Saturn IB, launchSuccessRate, 100 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSuccessRate Context triple: [Saturn IB, launchSuccessRate, 100 percent]
-
A.
successRate
chosen
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
-
B.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
C.
successfulLaunches
Indicates that one entity has carried out one or more launches that achieved their intended objectives without failure.
-
D.
launchFailures
Indicates that attempts to initiate or start an operation, process, or system have failed.
-
E.
successMetric
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb38464274819080f182b53783fa84 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:54 p.m.