Triple
T36722356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 8 |
E907100
|
entity |
| Predicate | dockingSucceeded |
P186032
|
FINISHED |
| Object | no |
—
|
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 | Statement: [Soyuz 8, dockingSucceeded, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockingSucceeded Context triple: [Soyuz 8, dockingSucceeded, no]
-
A.
dockingResult
chosen
Indicates the outcome or status produced when one entity attempts to dock or connect with another.
-
B.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
C.
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.
-
D.
dockingAttemptedWith
Indicates that one entity has initiated or carried out an attempt to dock with another entity, regardless of whether the docking ultimately succeeded.
-
E.
dockingModule
Indicates a relationship where one module is designed to connect and interface physically with another module, typically for docking or undocking operations.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.