Triple
T36096420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurs |
E1044073
|
entity |
| Predicate | typicalDockingTarget |
—
|
GENERATED |
| Object | Russian Orbital Segment of the ISS |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDockingTarget Context triple: [Kurs, typicalDockingTarget, Russian Orbital Segment of the ISS]
-
A.
intendedDockingPartner
Indicates that one entity is designated or expected to connect, interface, or dock with a specific counterpart as its planned partner.
-
B.
dockingSystemCompatibility
Indicates that two docking systems are capable of physically connecting and operating together as intended.
-
C.
hasDockingType
Indicates the specific docking configuration or method associated with an entity.
-
D.
hasDockingCapability
chosen
Indicates that an entity is capable of connecting or docking with another compatible entity or system.
-
E.
hasDockingPortType
Indicates that one entity possesses or is equipped with a docking port of a specified type or specification.
- F. None of above.
Provenance (1 batch)
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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.