Triple
T9413820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landing Zone 1 |
E226765
|
entity |
| Predicate | supportsRecoveryMethod |
P19129
|
FINISHED |
| Object | propulsive vertical landing |
—
|
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: propulsive vertical landing | Statement: [Landing Zone 1, supportsRecoveryMethod, propulsive vertical landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRecoveryMethod Context triple: [Landing Zone 1, supportsRecoveryMethod, propulsive vertical landing]
-
A.
recoveryMethod
chosen
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
B.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
C.
supportsBackupTool
Indicates that one entity provides compatibility with or functionality for a specified backup tool.
-
D.
recoveryConfiguration
Indicates a configuration relationship specifying how an entity should be restored, recovered, or brought back to an operational state after failure or disruption.
-
E.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c680e48190be82e3829e8711f0 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.