Triple
T12577885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX Cargo Dragon |
E300255
|
entity |
| Predicate | berthingOrDocking |
P54674
|
FINISHED |
| Object | autonomous docking |
—
|
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: autonomous docking | Statement: [SpaceX Cargo Dragon, berthingOrDocking, autonomous docking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: berthingOrDocking Context triple: [SpaceX Cargo Dragon, berthingOrDocking, autonomous docking]
-
A.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
B.
berthingSystem
Indicates a system or mechanism used to dock, moor, or secure one vehicle, vessel, or structure to another.
-
C.
docking
chosen
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
D.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
E.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 4:53 p.m.