Triple
T13127944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3 rocket |
E311891
|
entity |
| Predicate | testOutcome |
P58414
|
FINISHED |
| Object | largely unsuccessful |
—
|
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: largely unsuccessful | Statement: [A3 rocket, testOutcome, largely unsuccessful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testOutcome Context triple: [A3 rocket, testOutcome, largely unsuccessful]
-
A.
testResult
chosen
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
B.
testResultDisplay
Indicates how the outcome of a test is presented or shown to a viewer or system.
-
C.
testStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
D.
TestStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, is in progress, or has not yet been executed.
-
E.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.