Triple
T2013835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSF-67 |
E43747
|
entity |
| Predicate | launchMassInformation |
P7196
|
FINISHED |
| Object | partially classified |
—
|
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: partially classified | Statement: [USSF-67, launchMassInformation, partially classified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchMassInformation Context triple: [USSF-67, launchMassInformation, partially classified]
-
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.
launchVehicleSupported
Indicates that one entity provides the necessary infrastructure, capability, or compatibility to support the operation or use of a particular launch vehicle.
-
D.
launchEnvelope
Indicates initiating the sending or dispatching of an item or message, typically by packaging it into an envelope and starting its delivery process.
-
E.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b42d508190bf2b63132bb2ad77 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.