Triple
T37566114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 16 |
E933959
|
entity |
| Predicate | conductedExtravehicularActivities |
P24806
|
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: [Expedition 16, conductedExtravehicularActivities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductedExtravehicularActivities Context triple: [Expedition 16, conductedExtravehicularActivities, yes]
-
A.
spacewalksCount
Indicates the number of spacewalk activities an entity has performed or participated in.
-
B.
crewEVAPlanned
Indicates that a spacewalk (extravehicular activity) involving crew members is scheduled or planned to occur.
-
C.
spacewalks
chosen
Indicates that an astronaut performs activities outside a spacecraft in open space, typically while wearing a spacesuit and tethered or otherwise supported.
-
D.
numberOfEVAsOnMoon
Indicates the total count of extravehicular activities (spacewalks) that have occurred on the Moon.
-
E.
crewEVAHours
Indicates the total number of hours that crew members spend performing extravehicular activities (spacewalks) outside their vehicle or habitat.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.