Triple
T10022629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini spacecraft |
E200645
|
entity |
| Predicate | enabledEVA |
P91756
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gemini spacecraft, enabledEVA, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enabledEVA Context triple: [Gemini spacecraft, enabledEVA, yes]
-
A.
enabledBy
Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
-
B.
performedEVA
Indicates that an entity has carried out an extravehicular activity (EVA), such as a spacewalk, outside a spacecraft or space station.
-
C.
canEnable
Indicates that one entity has the capability or authority to activate, turn on, or make another entity or function operational.
-
D.
EVAobjective
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
E.
EVAType
Indicates the type or category of an extravehicular activity (EVA) associated with an entity, specifying what kind of EVA operation or event it represents.
- F. None of above. chosen
Provenance (4 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7ae36c8190896946be065fbf78 |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:53 p.m.