Triple
T16303572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Automated Transfer Vehicle program |
E395848
|
entity |
| Predicate | cargoDeliveredToISS |
P14976
|
FINISHED |
| Object | propellant |
—
|
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: propellant | Statement: [European Automated Transfer Vehicle program, cargoDeliveredToISS, propellant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoDeliveredToISS Context triple: [European Automated Transfer Vehicle program, cargoDeliveredToISS, propellant]
-
A.
deliveryToNASA
Indicates the action or arrangement of delivering something to NASA as the receiving organization.
-
B.
cargoCapacityFromISS
Indicates the amount of cargo capacity that is transported from the International Space Station to another location or vehicle.
-
C.
spaceStationLaunched
Indicates that a space station has been sent from Earth into space on a launch vehicle.
-
D.
cargoCapacityToISS
chosen
Indicates the amount of cargo that can be transported to the International Space Station in a given mission or by a given vehicle.
-
E.
installedOnISSDate
Indicates the date on which something was installed on the International Space Station (ISS).
- 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.