Triple
T14983997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Naval Shipyard |
E373653
|
entity |
| Predicate | dateOfOfficialClosureAsNavyBase |
P14100
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Philadelphia Naval Shipyard, dateOfOfficialClosureAsNavyBase, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfOfficialClosureAsNavyBase Context triple: [Philadelphia Naval Shipyard, dateOfOfficialClosureAsNavyBase, 1996]
-
A.
lastShipCommissioningDate
Indicates the date on which the most recently commissioned ship in a given context was officially placed into active service.
-
B.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
establishedAsNavalBase
Indicates that a location was formally designated and put into use as a naval base.
-
D.
decommissionedFromRoyalNavy
Indicates that a vessel or asset has been formally retired from active service in the Royal Navy.
-
E.
servesAsNavalAirStationFor
Indicates that one entity functions as a naval air station providing aviation facilities and support for another entity (such as a navy, fleet, or military force).
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6ff4a7c8190ab7554f3a1a09b67 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.