Triple
T27655195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS Node 1 |
E696973
|
entity |
| Predicate | hasTypeOfDockingPort |
P131901
|
FINISHED |
| Object | Common Berthing Mechanism |
—
|
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: Common Berthing Mechanism | Statement: [ISS Node 1, hasTypeOfDockingPort, Common Berthing Mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDockingPort Context triple: [ISS Node 1, hasTypeOfDockingPort, Common Berthing Mechanism]
-
A.
hasDockingPortType
chosen
Indicates that one entity possesses or is equipped with a docking port of a specified type or specification.
-
B.
hasDockingType
Indicates the specific docking configuration or method associated with an entity.
-
C.
usedWithDockingPortType
Indicates that one entity is designed or configured to be used together with a specific type of docking port.
-
D.
hasDockType
Indicates the specific type or category of dock 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.
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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 2:34 p.m.