Triple
T4545183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmony |
E110027
|
entity |
| Predicate | hasDockingPort |
P14980
|
FINISHED |
| Object | forward Common Berthing Mechanism port |
—
|
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: forward Common Berthing Mechanism port | Statement: [Harmony, hasDockingPort, forward Common Berthing Mechanism port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDockingPort Context triple: [Harmony, hasDockingPort, forward Common Berthing Mechanism port]
-
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.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
C.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.