Triple
T4214812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayabusa |
E94188
|
entity |
| Predicate | capsuleRecoverySupport |
P19129
|
FINISHED |
| Object | Australian authorities |
—
|
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: Australian authorities | Statement: [Hayabusa, capsuleRecoverySupport, Australian authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capsuleRecoverySupport Context triple: [Hayabusa, capsuleRecoverySupport, Australian authorities]
-
A.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
B.
launchAndRecovery
Indicates a relationship where one entity is responsible for both deploying (launching) another entity into operation and subsequently retrieving (recovering) it afterward.
-
C.
capsule
Indicates that one entity is a capsule containing, enclosing, or encapsulating another entity.
-
D.
rocketCoreRecovery
Indicates the process or outcome of retrieving and securing the main rocket core after its launch or mission.
-
E.
recoveryMethod
chosen
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.