Triple
T10936125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County-class destroyer |
E258335
|
entity |
| Predicate | hasHullClassification |
P6097
|
FINISHED |
| Object | destroyer |
—
|
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 | Statement: [County-class destroyer, hasHullClassification, destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHullClassification Context triple: [County-class destroyer, hasHullClassification, destroyer]
-
A.
hasHullType
chosen
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
B.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
D.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
E.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
- 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.