Triple
T12593592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamashiro escort destroyers |
E300671
|
entity |
| Predicate | typeOfVesselEscorted |
P105591
|
FINISHED |
| Object | battleship |
—
|
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: battleship | Statement: [Yamashiro escort destroyers, typeOfVesselEscorted, battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVesselEscorted Context triple: [Yamashiro escort destroyers, typeOfVesselEscorted, battleship]
-
A.
convoyType
Indicates the specific kind or classification of convoy associated with or used in the relationship between the entities.
-
B.
convoyProtected
Indicates that one entity provides protective escort or defense to a moving group (convoy) of other entities during transit.
-
C.
governmentVessel
Indicates that the vessel is owned, operated, or officially designated for use by a government or governmental authority.
-
D.
garrisonVessel
Indicates that a vessel is stationed at or assigned to serve as a garrison or defensive presence at a particular location.
-
E.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
- F. None of above. chosen
Provenance (4 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954e351f88190869220d46e0ce282 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 5:07 p.m.