Triple
T36118427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 6 |
E1044672
|
entity |
| Predicate | forwardDockingPortUsedBy |
P156598
|
FINISHED |
| Object | Progress spacecraft |
—
|
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: Progress spacecraft | Statement: [Salyut 6, forwardDockingPortUsedBy, Progress spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forwardDockingPortUsedBy Context triple: [Salyut 6, forwardDockingPortUsedBy, Progress spacecraft]
-
A.
hasDockingPortType
Indicates that one entity possesses or is equipped with a docking port of a specified type or specification.
-
B.
hasPortUse
chosen
Indicates that one entity utilizes or is assigned to a particular port for access, communication, or operation.
-
C.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
D.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
E.
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.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.