Triple
T16303225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-II Transfer Vehicle |
E395840
|
entity |
| Predicate | missionSuccessRate |
P7192
|
FINISHED |
| Object | 100% |
—
|
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: 100% | Statement: [H-II Transfer Vehicle, missionSuccessRate, 100%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSuccessRate Context triple: [H-II Transfer Vehicle, missionSuccessRate, 100%]
-
A.
successRate
chosen
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
-
B.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
C.
numberOfSuccessfulMissions
Indicates the count of missions that have been completed successfully by the referenced entity or within the specified context.
-
D.
successMetric
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
E.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.