Triple
T26699333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Miller (FF-1091) |
E673106
|
entity |
| Predicate | navalRegisterStatus |
P130838
|
FINISHED |
| Object | stricken |
—
|
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: stricken | Statement: [USS Miller (FF-1091), navalRegisterStatus, stricken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalRegisterStatus Context triple: [USS Miller (FF-1091), navalRegisterStatus, stricken]
-
A.
navyListStatus
chosen
Indicates the status or classification of an entity within a navy’s official list or registry.
-
B.
navalPowerStatus
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
-
C.
NavyRegistry
Indicates a formal registration or listing of an entity within an official navy or naval organization.
-
D.
workStatus_OnTheCatalogueOfShips
Indicates that a work’s status is determined by whether it appears in the Catalogue of Ships section of the text.
-
E.
navalAffiliation
Indicates a formal relationship in which an entity is associated with, belongs to, or operates under a particular navy or naval force.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:30 a.m.