Triple
T27700645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS John F. Kennedy (CVN-79) |
E698418
|
entity |
| Predicate | keelLaidDate |
P33569
|
FINISHED |
| Object | 2015-08-22 |
—
|
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: 2015-08-22 | Statement: [USS John F. Kennedy (CVN-79), keelLaidDate, 2015-08-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keelLaidDate Context triple: [USS John F. Kennedy (CVN-79), keelLaidDate, 2015-08-22]
-
A.
dateOfKeelLaying
chosen
Indicates the calendar date on which the keel of a vessel was formally laid, marking the official start of its construction.
-
B.
keelLaidFor
Indicates that the initial structural construction (keel laying) of a vessel has been formally started for a particular ship or project.
-
C.
shipCommissionedDate
Indicates the date on which a ship was officially commissioned into service.
-
D.
hullConstructedIn
Indicates that the hull of an object (such as a ship or vessel) was built or constructed at a specific location or facility.
-
E.
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).
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a29ff08190bfd246ccaf0ddb4e |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:56 p.m.