Triple
T31704957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 82 destroyer |
E809152
|
entity |
| Predicate | HMSBristolLaterRole |
P164509
|
FINISHED |
| Object | training and accommodation ship |
—
|
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: training and accommodation ship | Statement: [Type 82 destroyer, HMSBristolLaterRole, training and accommodation ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HMSBristolLaterRole Context triple: [Type 82 destroyer, HMSBristolLaterRole, training and accommodation ship]
-
A.
navalRoleAfterConversion
chosen
Indicates the naval role or function an entity assumes after it has been converted or repurposed from its original state.
-
B.
shipHistoricalRole
Indicates the historical function or significance a ship had, such as its role in events, conflicts, or periods of service.
-
C.
RoyalNavyDesignation
Indicates that an entity has been assigned an official designation or identifier by the Royal Navy.
-
D.
HMSInvincibleFate
Indicates the ultimate outcome or destiny that befell HMS Invincible, such as its loss, decommissioning, or other final status.
-
E.
inUseAsRoyalNavyEnsignUntil
Indicates that something served as the Royal Navy ensign up to a specified end date.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:13 p.m.