Triple
T27609807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest Joint Airlock |
E700281
|
entity |
| Predicate | supportsSpacesuitType |
P157980
|
FINISHED |
| Object | Extravehicular Mobility Unit |
—
|
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: Extravehicular Mobility Unit | Statement: [Quest Joint Airlock, supportsSpacesuitType, Extravehicular Mobility Unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSpacesuitType Context triple: [Quest Joint Airlock, supportsSpacesuitType, Extravehicular Mobility Unit]
-
A.
spaceSuitUsed
Indicates that a particular space suit is employed or worn in the performance of an activity or mission by an entity.
-
B.
spaceSuitSystem
Indicates a relationship where an entity functions as a system or subsystem that is part of, or integral to, a space suit.
-
C.
isOnSpacecraftType
Indicates that one entity is currently aboard or assigned to a spacecraft of a specified type.
-
D.
spacewalksSupported
chosen
Indicates that the entity is capable of supporting or enabling spacewalk activities for astronauts.
-
E.
spacecraftTypeSupported
Indicates that a system, facility, or service is capable of accommodating or operating a specified type of spacecraft.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 27, 2026, 2:10 p.m.