Triple
T36096420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurs |
E1044073
|
entity |
| Predicate | typicalDockingTarget |
P188833
|
FINISHED |
| Object | Russian Orbital Segment of the ISS |
E1181930
|
NE 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: Russian Orbital Segment of the ISS | Statement: [Kurs, typicalDockingTarget, Russian Orbital Segment of the ISS]
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 (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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39340007f08190a53738807251cd14 |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.