Triple
T2864410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Launch Alliance |
E63402
|
entity |
| Predicate | notableMissionType |
P22637
|
FINISHED |
| Object | interplanetary missions |
—
|
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: interplanetary missions | Statement: [United Launch Alliance, notableMissionType, interplanetary missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMissionType Context triple: [United Launch Alliance, notableMissionType, interplanetary missions]
-
A.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
-
C.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
D.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
E.
notableManeuver
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb853908190aa2fd492e9fa5e87 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.