Triple
T10792577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Leonard F. Mason |
E254617
|
entity |
| Predicate | reclassified |
P22031
|
FINISHED |
| Object | radar picket destroyer |
—
|
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: radar picket destroyer | Statement: [USS Leonard F. Mason, reclassified, radar picket destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassified Context triple: [USS Leonard F. Mason, reclassified, radar picket destroyer]
-
A.
reclassifiedAs
chosen
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
B.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
C.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
D.
reallocated
Indicates that something previously assigned or distributed to one entity, purpose, or location has been assigned or distributed again to a different one.
-
E.
reincorporated
Indicates that an entity has been formed again or brought back into existence as a corporation after having previously ceased or changed its corporate status.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f7ad408190af4727dd9d459498 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.