Triple
T1945029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Russell (DD-414) |
E42041
|
entity |
| Predicate | scrappedIn |
P16228
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [USS Russell (DD-414), scrappedIn, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrappedIn Context triple: [USS Russell (DD-414), scrappedIn, 1948]
-
A.
scrappedAt
chosen
Indicates the time or date at which something was discarded, decommissioned, or removed from use.
-
B.
scrapped
Indicates that something planned, created, or in progress was abandoned, discarded, or cancelled and will no longer be pursued or used.
-
C.
soldForScrap
Indicates that something was disposed of or transferred specifically to be broken down and recycled for its material value rather than used in its original form.
-
D.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
E.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb32ebae881908f7541301f0198ae |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.