Triple
T197925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 1 |
E4038
|
entity |
| Predicate | massAtLaunch |
P7196
|
FINISHED |
| Object | about 825.5 kilograms |
—
|
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: about 825.5 kilograms | Statement: [Voyager 1, massAtLaunch, about 825.5 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massAtLaunch Context triple: [Voyager 1, massAtLaunch, about 825.5 kilograms]
-
A.
launchMass
chosen
Indicates the total mass of an object or payload at the moment it is launched.
-
B.
launchVehicle
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.
-
C.
massRelativeToEarth
Indicates the comparative amount of mass an entity has relative to the mass of Earth.
-
D.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
E.
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.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.