Triple
T16303381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jules Verne (ATV-1) |
E395844
|
entity |
| Predicate | firstDockingDate |
P91758
|
FINISHED |
| Object | 2008-04-03 |
—
|
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: 2008-04-03 | Statement: [Jules Verne (ATV-1), firstDockingDate, 2008-04-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDockingDate Context triple: [Jules Verne (ATV-1), firstDockingDate, 2008-04-03]
-
A.
firstSuccessfulDockingDate
chosen
Indicates the calendar date on which the first successful docking between the relevant entities occurred.
-
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.
firstISSBerthingYear
Indicates the calendar year in which a spacecraft or module first berthed with the International Space Station.
-
D.
firstSuccessfulDockingWith
Indicates that one entity is the first other entity with which the subject successfully completed a docking operation.
-
E.
undockingDate
Indicates the date on which one object or vehicle separates and moves away from another to which it was previously docked.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.