Triple
T21312802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-91 |
E525384
|
entity |
| Predicate | dockedWithMir |
P143686
|
FINISHED |
| Object | 1998-06-04 |
—
|
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: 1998-06-04 | Statement: [STS-91, dockedWithMir, 1998-06-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockedWithMir Context triple: [STS-91, dockedWithMir, 1998-06-04]
-
A.
firstDockingDateWithMir
Indicates the date on which an entity first performed a docking with the Mir space station.
-
B.
dockingSystem
Indicates a relationship where one structure or vehicle is equipped with or connected to a system that enables secure docking with another compatible structure or vehicle.
-
C.
dockingWithISS
Indicates a relationship where a spacecraft is physically connecting and securing itself to the International Space Station to enable transfer of crew, cargo, or resources.
-
D.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
E.
hasDockingType
Indicates the specific docking configuration or method associated with an entity.
- F. None of above. chosen
Provenance (4 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcb45f08190a9bcaa366964a2cb |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:25 p.m.