Triple
T12794476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJ-60A solid rocket booster |
E305853
|
entity |
| Predicate | missionTypes |
P22637
|
FINISHED |
| Object | commercial satellite launches |
—
|
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: commercial satellite launches | Statement: [AJ-60A solid rocket booster, missionTypes, commercial satellite launches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionTypes Context triple: [AJ-60A solid rocket booster, missionTypes, commercial satellite launches]
-
A.
missionTypeSupport
Indicates that one entity provides support or assistance to another within the context of a specific mission or operation.
-
B.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
D.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
E.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6ca0288190aba01735b71a01da |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.