Triple
T24277067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Renville |
E605436
|
entity |
| Predicate | NavyListStatus |
P130838
|
FINISHED |
| Object | struck from Naval Vessel Register |
—
|
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: struck from Naval Vessel Register | Statement: [USS Renville, NavyListStatus, struck from Naval Vessel Register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NavyListStatus Context triple: [USS Renville, NavyListStatus, struck from Naval Vessel Register]
-
A.
navyListStatus
chosen
Indicates the status or classification of an entity within a navy’s official list or registry.
-
B.
NavyRegistry
Indicates a formal registration or listing of an entity within an official navy or naval organization.
-
C.
navalPowerStatus
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
-
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.
naveStatus
Indicates the operational or functional status currently assigned to a nave or central area within a structure.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5fd03481908e502c6944d7fe69 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.