Triple
T1116683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn V |
E11115
|
entity |
| Predicate | launchSuccesses |
P7189
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Saturn V, launchSuccesses, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSuccesses Context triple: [Saturn V, launchSuccesses, 13]
-
A.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
B.
successfulLaunches
chosen
Indicates that one entity has carried out one or more launches that achieved their intended objectives without failure.
-
C.
failedLaunches
Indicates that one or more attempts to launch something (e.g., a product, project, or mission) did not succeed.
-
D.
helpedLaunch
Indicates that one entity played a significant role in initiating, starting, or bringing another entity (such as a project, product, or organization) into operation or public release.
-
E.
successRate
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.