Triple
T36514414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 3 |
E899997
|
entity |
| Predicate | dockingAttemptedWith |
P185798
|
FINISHED |
| Object | Soyuz 2 |
—
|
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: Soyuz 2 | Statement: [Soyuz 3, dockingAttemptedWith, Soyuz 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockingAttemptedWith Context triple: [Soyuz 3, dockingAttemptedWith, Soyuz 2]
-
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.
usedWithDockingPortType
Indicates that one entity is designed or configured to be used together with a specific type of docking port.
-
D.
hasDockingType
Indicates the specific docking configuration or method associated with an entity.
-
E.
dockingSystemCompatibility
Indicates that two docking systems are capable of physically connecting and operating together as intended.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.