Triple
T10936223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Sheffield (D80) |
E258337
|
entity |
| Predicate | IMOorPennantType |
P3153
|
FINISHED |
| Object | destroyer pennant number D80 |
—
|
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: destroyer pennant number D80 | Statement: [HMS Sheffield (D80), IMOorPennantType, destroyer pennant number D80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IMOorPennantType Context triple: [HMS Sheffield (D80), IMOorPennantType, destroyer pennant number D80]
-
A.
isWarEnsignOf
Indicates that one entity is the war ensign (a specific military or wartime flag) representing or belonging to another entity.
-
B.
isCivilEnsignOf
Indicates that an object is the civil (non-military) ensign or flag officially used to represent a particular entity, typically a country or territory.
-
C.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
D.
pennantNumber
chosen
Indicates the identifying pennant number assigned to a ship or naval vessel.
-
E.
isOnFlagOf
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770afaa1c8190b8fced9c694c0938 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.