Triple
T4214869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JAXA Astronaut Group |
E94189
|
entity |
| Predicate | hasTrainingFor |
P54797
|
FINISHED |
| Object | extravehicular activity |
—
|
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: extravehicular activity | Statement: [JAXA Astronaut Group, hasTrainingFor, extravehicular activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingFor Context triple: [JAXA Astronaut Group, hasTrainingFor, extravehicular activity]
-
A.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
B.
hasTrained
Indicates that one entity has provided training or instruction to another entity.
-
C.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
D.
requiresTraining
Indicates that one entity can only be properly or legitimately used, performed, or engaged with if the other entity has first received appropriate training.
-
E.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:04 p.m.