Triple
T21157109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Croaker (SS-246) |
E521340
|
entity |
| Predicate | reclassifiedOn |
P124704
|
FINISHED |
| Object | 18 February 1953 |
—
|
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: 18 February 1953 | Statement: [USS Croaker (SS-246), reclassifiedOn, 18 February 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassifiedOn Context triple: [USS Croaker (SS-246), reclassifiedOn, 18 February 1953]
-
A.
reclassifiedDate
chosen
Indicates the date on which something’s classification or status was changed from its previous category to a new one.
-
B.
reclassifiedAs
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
C.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
D.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
E.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252c6db08190bcdffc3f2cfc6138 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.