Triple
T17426750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCI |
E423756
|
entity |
| Predicate | separationFromSpacecraft |
P127409
|
FINISHED |
| Object | deployed from Hayabusa2 near Ryugu |
—
|
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: deployed from Hayabusa2 near Ryugu | Statement: [SCI, separationFromSpacecraft, deployed from Hayabusa2 near Ryugu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationFromSpacecraft Context triple: [SCI, separationFromSpacecraft, deployed from Hayabusa2 near Ryugu]
-
A.
separationFromOrbiterDate
Indicates the date on which a spacecraft or module separates from its associated orbiter.
-
B.
typicalSeparationBetweenSatellites
Indicates the usual distance maintained between satellites in a given configuration or orbital arrangement.
-
C.
hostSpacecraft
Indicates that one entity serves as the platform or carrier on which another spacecraft is mounted, accommodated, or operated.
-
D.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
-
E.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
- F. None of above. chosen
Provenance (4 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fcbf54819091babed0b9b05716 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.