Triple
T22972428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Albacore (AGSS-569) |
E571222
|
entity |
| Predicate | statusAfterDecommissioning |
P48589
|
FINISHED |
| Object | placed in reserve |
—
|
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: placed in reserve | Statement: [USS Albacore (AGSS-569), statusAfterDecommissioning, placed in reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterDecommissioning Context triple: [USS Albacore (AGSS-569), statusAfterDecommissioning, placed in reserve]
-
A.
decommissioningStatus
chosen
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
B.
estimatedDecommissioningDuration
Indicates the expected length of time required to complete the decommissioning process of an entity.
-
C.
statusAfterRelocation
Indicates the condition or state an entity has once it has been moved from its original location to a new one.
-
D.
statusAfterSupersession
Indicates the status or condition an entity holds after it has been superseded by another entity.
-
E.
statusAfterRestoration
Indicates the condition or state an entity has once a restoration process has been completed.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182343a448190a5259cdf721c9d04 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.