Triple
T7128419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Langley (CVL-27) |
E166124
|
entity |
| Predicate | struckFromNavalRegister |
P10294
|
FINISHED |
| Object | 1959-11-01 |
—
|
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: 1959-11-01 | Statement: [USS Langley (CVL-27), struckFromNavalRegister, 1959-11-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: struckFromNavalRegister Context triple: [USS Langley (CVL-27), struckFromNavalRegister, 1959-11-01]
-
A.
strickenFromNavalRegister
chosen
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
-
B.
decommissionedAsWorkingVessel
Indicates that an entity has been officially retired from service and is no longer used as an active working vessel.
-
C.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
D.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
E.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66b230c819090ddbc5396868305 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.