Triple
T12738327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exploration Flight Test 1 |
E304421
|
entity |
| Predicate | testedEnvironment |
P37296
|
FINISHED |
| Object | high Earth orbit |
—
|
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: high Earth orbit | Statement: [Exploration Flight Test 1, testedEnvironment, high Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedEnvironment Context triple: [Exploration Flight Test 1, testedEnvironment, high Earth orbit]
-
A.
launchEnvironment
chosen
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
B.
testedOn
Indicates that an entity has been used as the subject or material in a test, experiment, or evaluation performed by another entity.
-
C.
testedProcess
Indicates that an entity has performed a test or evaluation on a specific process.
-
D.
testedWith
Indicates that one entity has been examined, evaluated, or verified using another entity as the test method, tool, or counterpart.
-
E.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.