Triple
T27356707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Development Flight Instrumentation |
E685703
|
entity |
| Predicate | installedForMissionType |
P17730
|
FINISHED |
| Object | orbital flight tests |
—
|
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: orbital flight tests | Statement: [Development Flight Instrumentation, installedForMissionType, orbital flight tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedForMissionType Context triple: [Development Flight Instrumentation, installedForMissionType, orbital flight tests]
-
A.
appliesToMission
Indicates that something (such as a rule, condition, resource, or parameter) is relevant or applicable to a specific mission.
-
B.
installedDuringServicingMission
Indicates that one entity was installed onto or into another entity specifically as part of a servicing mission.
-
C.
installedFor
Indicates that something has been set up or put in place to be used by or on behalf of a particular entity.
-
D.
supportsMissionType
chosen
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
E.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 11:51 a.m.