Triple
T36196823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Bainbridge (DD-1) |
E1047149
|
entity |
| Predicate | soldForScrapTo |
P12194
|
FINISHED |
| Object | Henry A. Hitner’s Sons Company |
—
|
NE NERFINISHED |
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: Henry A. Hitner’s Sons Company | Statement: [USS Bainbridge (DD-1), soldForScrapTo, Henry A. Hitner’s Sons Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldForScrapTo Context triple: [USS Bainbridge (DD-1), soldForScrapTo, Henry A. Hitner’s Sons Company]
-
A.
soldForScrap
chosen
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.
-
B.
scrappedTo
Indicates that something has been discarded, dismantled, or removed in order to be replaced or converted into another specified thing or state.
-
C.
scrappedAt
Indicates the time or date at which something was discarded, decommissioned, or removed from use.
-
D.
placeScrapped
Indicates that a place has been dismantled, discarded, or removed from use.
-
E.
scrappedAfter
Indicates that one entity was discarded, removed, or abandoned after another specified event or entity in time.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.