Triple
T4214826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayabusa |
E94188
|
entity |
| Predicate | reentryEvent |
P30129
|
FINISHED |
| Object | spacecraft bus burned up in Earth’s atmosphere |
—
|
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: spacecraft bus burned up in Earth’s atmosphere | Statement: [Hayabusa, reentryEvent, spacecraft bus burned up in Earth’s atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryEvent Context triple: [Hayabusa, reentryEvent, spacecraft bus burned up in Earth’s atmosphere]
-
A.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
B.
reentryProfile
chosen
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
C.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
D.
detentionEvent
Indicates an event in which an entity is formally held, confined, or kept in custody, typically by an authority, for a period of time.
-
E.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
- 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.