Triple
T37997147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-21 |
E947989
|
entity |
| Predicate | issModuleUsedForBerthingOrDocking |
P14974
|
FINISHED |
| Object | Harmony |
—
|
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: Harmony | Statement: [SpaceX CRS-21, issModuleUsedForBerthingOrDocking, Harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issModuleUsedForBerthingOrDocking Context triple: [SpaceX CRS-21, issModuleUsedForBerthingOrDocking, Harmony]
-
A.
berthingOrDockingTarget
chosen
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.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
D.
docking
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.