Triple
T9807866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo–Soyuz Docking Module |
E238196
|
entity |
| Predicate | dockingSystemType |
P14980
|
FINISHED |
| Object | androgynous docking system |
—
|
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: androgynous docking system | Statement: [Apollo–Soyuz Docking Module, dockingSystemType, androgynous docking system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockingSystemType Context triple: [Apollo–Soyuz Docking Module, dockingSystemType, androgynous docking system]
-
A.
dockingSystem
chosen
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.
-
B.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
C.
operatedDock
Indicates that an entity managed or controlled the functioning of a dock or docking facility.
-
D.
hasDockType
Indicates the specific type or category of dock associated with an entity.
-
E.
berthingSystem
Indicates a system or mechanism used to dock, moor, or secure one vehicle, vessel, or structure to another.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7ddaac8190a5584a5c863fbaa3 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.