Triple
T38092682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus Laboratory Module |
E951153
|
entity |
| Predicate | firstCrewIngressDate |
—
|
GENERATED |
| Object | 2008-02-13 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCrewIngressDate Context triple: [Columbus Laboratory Module, firstCrewIngressDate, 2008-02-13]
-
A.
firstCrewBoarded
chosen
Indicates that the initial group of crew members has boarded or entered a specified vehicle, vessel, or location.
-
B.
firstEntranceClearedDate
Indicates the date on which an entity’s initial entrance, access, or admission was officially cleared or approved.
-
C.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
D.
dateOfFirstCrewedLaunch
Indicates the calendar date on which the first crewed (human-occupied) launch associated with the subject took place.
-
E.
firstCrewMember
Indicates that the subject is the first (earliest or primary) member within a specified crew or group.
- F. None of above.
Provenance (1 batch)
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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.