Triple
T38092682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus Laboratory Module |
E951153
|
entity |
| Predicate | firstCrewIngressDate |
P64928
|
FINISHED |
| Object | 2008-02-13 |
—
|
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: 2008-02-13 | Statement: [Columbus Laboratory Module, firstCrewIngressDate, 2008-02-13]
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 (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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.