Triple
T10936220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Sheffield (D80) |
E258337
|
entity |
| Predicate | shipNumberInClass |
P96724
|
FINISHED |
| Object | lead ship of the Type 42 class |
—
|
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: lead ship of the Type 42 class | Statement: [HMS Sheffield (D80), shipNumberInClass, lead ship of the Type 42 class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipNumberInClass Context triple: [HMS Sheffield (D80), shipNumberInClass, lead ship of the Type 42 class]
-
A.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
B.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
D.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
E.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
- 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_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. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.