Triple
T11692425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Resupply Services 1 |
E277900
|
entity |
| Predicate | unberthingDate |
P37019
|
FINISHED |
| Object | 2012-10-28 |
—
|
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: 2012-10-28 | Statement: [Commercial Resupply Services 1, unberthingDate, 2012-10-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unberthingDate Context triple: [Commercial Resupply Services 1, unberthingDate, 2012-10-28]
-
A.
undockingDate
chosen
Indicates the date on which one object or vehicle separates and moves away from another to which it was previously docked.
-
B.
dockingDate
Indicates the date on which one entity physically docks with or is scheduled to dock with another (e.g., a vehicle, vessel, or spacecraft).
-
C.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
D.
departureDateOnFinalVoyage
Indicates the date on which an entity began its final voyage or last recorded journey.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47a3ddc819098e208611148d15b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.