Triple
T36514415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 3 |
E899997
|
entity |
| Predicate | dockingResult |
P186032
|
FINISHED |
| Object | no hard docking achieved |
—
|
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: no hard docking achieved | Statement: [Soyuz 3, dockingResult, no hard docking achieved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockingResult Context triple: [Soyuz 3, dockingResult, no hard docking achieved]
-
A.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
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.
dockingAxis
Indicates the primary directional line or orientation along which one object is intended to connect, align, or dock with another.
-
D.
dockingModule
Indicates a relationship where one module is designed to connect and interface physically with another module, typically for docking or undocking operations.
-
E.
dockingDate
Indicates the date on which one entity physically docks with or is scheduled to dock with another (e.g., a vehicle, vessel, or spacecraft).
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:10 p.m.