Triple
T31610121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS American Victory |
E806601
|
entity |
| Predicate | placedInReserveFleet |
P71597
|
FINISHED |
| Object | James River Reserve Fleet |
—
|
NE NERFINISHED |
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: James River Reserve Fleet | Statement: [SS American Victory, placedInReserveFleet, James River Reserve Fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placedInReserveFleet Context triple: [SS American Victory, placedInReserveFleet, James River Reserve Fleet]
-
A.
placedInReserve
chosen
Indicates that an entity has been set aside or allocated into a reserve, rather than being used or kept in general circulation.
-
B.
fleetDisposition
Indicates how a fleet is arranged, positioned, or distributed relative to its elements or environment.
-
C.
decommissionedFromUSN
Indicates that something was formally retired or removed from active service in the United States Navy.
-
D.
yearsInReserve
Indicates the number of years an entity has been held or maintained in reserve before being used, deployed, or activated.
-
E.
establishedAsReserve
Indicates that an area or resource has been formally designated and set aside as a reserve for protection or special management.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 30, 2026, 10:36 p.m.