Triple
T17359406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-V rocket |
E422027
|
entity |
| Predicate | launchOfHayabusa |
P4020
|
FINISHED |
| Object | 2003-05-09 |
—
|
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: 2003-05-09 | Statement: [M-V rocket, launchOfHayabusa, 2003-05-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchOfHayabusa Context triple: [M-V rocket, launchOfHayabusa, 2003-05-09]
-
A.
spacecraftLaunchAssociatedWith
Indicates a relationship where a spacecraft launch is connected or linked to another event, object, or entity involved in or affected by that launch.
-
B.
launchDateOfExplorer1
Indicates the date on which the spacecraft Explorer 1 was launched.
-
C.
isFirstSpacecraftTo
Indicates that a spacecraft is the earliest or initial one to reach, visit, or achieve a specified destination or milestone.
-
D.
launchVehicle
chosen
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
E.
lunarMissionCommanded
Indicates that an entity served as the commanding leader of a specified lunar mission.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4be7448190988593ee342348c1 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.