Triple
T4570045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boe-CFT |
E123007
|
entity |
| Predicate | missionProfileElement |
P23258
|
FINISHED |
| Object | launch on Atlas V |
—
|
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: launch on Atlas V | Statement: [Boe-CFT, missionProfileElement, launch on Atlas V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionProfileElement Context triple: [Boe-CFT, missionProfileElement, launch on Atlas V]
-
A.
missionProfile
Indicates the specific set of objectives, conditions, and operational parameters that define how a mission is planned, conducted, and evaluated.
-
B.
missionCharacteristic
chosen
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
-
C.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
D.
missionScope
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
-
E.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c3eba48190af1fce6e1ca16943 |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.