Triple
T34748508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion thermal protection system |
E1001702
|
entity |
| Predicate | testedOnMission |
P53282
|
FINISHED |
| Object | Exploration Flight Test 1 |
—
|
NE NERFINISHED |
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: Exploration Flight Test 1 | Statement: [Orion thermal protection system, testedOnMission, Exploration Flight Test 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedOnMission Context triple: [Orion thermal protection system, testedOnMission, Exploration Flight Test 1]
-
A.
operatedOnMission
Indicates that an agent carried out or participated in the execution of a specific mission.
-
B.
usedByMission
chosen
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
C.
appliesToMission
Indicates that something (such as a rule, condition, resource, or parameter) is relevant or applicable to a specific mission.
-
D.
sampledDuringMission
Indicates that one entity was collected or sampled in the course of a specific mission involving the other entity.
-
E.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.