Triple
T26529629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B1061 |
E670783
|
entity |
| Predicate | launchedMissionType |
P22637
|
FINISHED |
| Object | cargo resupply mission |
—
|
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: cargo resupply mission | Statement: [B1061, launchedMissionType, cargo resupply mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedMissionType Context triple: [B1061, launchedMissionType, cargo resupply mission]
-
A.
notableMissionLaunched
Indicates that an entity (such as a space agency or organization) has launched a mission that is considered notable or significant.
-
B.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
missionTypeEstablished
Indicates that a specific type or category of mission has been formally defined and put into effect.
-
D.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
E.
missionTypeSupport
Indicates that one entity provides support or assistance to another within the context of a specific mission or 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 1:34 a.m.