Triple
T5989562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS San Francisco (CA-38) |
E133310
|
entity |
| Predicate | soldForScrapDate |
P12194
|
FINISHED |
| Object | 9 September 1959 |
—
|
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: 9 September 1959 | Statement: [USS San Francisco (CA-38), soldForScrapDate, 9 September 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldForScrapDate Context triple: [USS San Francisco (CA-38), soldForScrapDate, 9 September 1959]
-
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.
scrappedAt
Indicates the time or date at which something was discarded, decommissioned, or removed from use.
-
C.
scrappedAfter
Indicates that one entity was discarded, removed, or abandoned after another specified event or entity in time.
-
D.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc76fd481908cc3f327e532a1a6 |
completed | March 22, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.