Triple
T13529034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvant-1 |
E323083
|
entity |
| Predicate | hadDockingPortFor |
P14980
|
FINISHED |
| Object | visiting spacecraft |
—
|
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: visiting spacecraft | Statement: [Kvant-1, hadDockingPortFor, visiting spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadDockingPortFor Context triple: [Kvant-1, hadDockingPortFor, visiting spacecraft]
-
A.
supportsDockingStations
Indicates that one entity is compatible with and can function correctly when connected to docking stations associated with another entity.
-
B.
hasDockType
Indicates the specific type or category of dock associated with an entity.
-
C.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
D.
hasDryDock
Indicates that one entity possesses, contains, or is equipped with a dry dock facility used for servicing or repairing vessels out of the water.
-
E.
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.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafba2c308190873efd15dfe26358 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.