Triple
T7727712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew Dragon Demo-2 |
E175174
|
entity |
| Predicate | issDockingDate |
P37018
|
FINISHED |
| Object | 2020-05-31 |
—
|
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: 2020-05-31 | Statement: [Crew Dragon Demo-2, issDockingDate, 2020-05-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issDockingDate Context triple: [Crew Dragon Demo-2, issDockingDate, 2020-05-31]
-
A.
dockingDate
chosen
Indicates the date on which one entity physically docks with or is scheduled to dock with another (e.g., a vehicle, vessel, or spacecraft).
-
B.
undockingDate
Indicates the date on which one object or vehicle separates and moves away from another to which it was previously docked.
-
C.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
D.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
E.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:06 p.m.