Triple
T27075388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceX CRS-11 |
E685448
|
entity |
| Predicate | dockingOrBerthingDate |
P37018
|
FINISHED |
| Object | 2017-06-05 |
—
|
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: 2017-06-05 | Statement: [SpaceX CRS-11, dockingOrBerthingDate, 2017-06-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dockingOrBerthingDate Context triple: [SpaceX CRS-11, dockingOrBerthingDate, 2017-06-05]
-
A.
dockingDate
chosen
Indicates the date on which one entity physically docks with or is scheduled to dock with another (e.g., a vehicle, vessel, or spacecraft).
-
B.
undockingDate
Indicates the date on which one object or vehicle separates and moves away from another to which it was previously docked.
-
C.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
D.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
E.
shipCommissionedDate
Indicates the date on which a ship was officially commissioned into service.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623159a7c819089028373790db00f |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:31 a.m.