Triple
T28091936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-31 |
E709975
|
entity |
| Predicate | dockedToModule |
P54674
|
FINISHED |
| Object | Zvezda service module |
—
|
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: Zvezda service module | Statement: [Soyuz TM-31, dockedToModule, Zvezda service module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockedToModule Context triple: [Soyuz TM-31, dockedToModule, Zvezda service module]
-
A.
dockingModule
Indicates a relationship where one module is designed to connect and interface physically with another module, typically for docking or undocking operations.
-
B.
dockingModuleOrigin
Indicates the original source or location from which a docking module comes or was deployed.
-
C.
docking
chosen
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
D.
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.
-
E.
dockedWithMir
Indicates that one object or vehicle has physically docked with the Mir space station, forming a temporary connected configuration.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6406afe448190ad9c61220d2573b4 |
completed | May 2, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:59 p.m.