Triple
T30301798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD |
E770669
|
entity |
| Predicate | appliesToVesselType |
P90718
|
FINISHED |
| Object | guided-missile destroyer (historically before DDG split) |
—
|
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: guided-missile destroyer (historically before DDG split) | Statement: [DD, appliesToVesselType, guided-missile destroyer (historically before DDG split)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToVesselType Context triple: [DD, appliesToVesselType, guided-missile destroyer (historically before DDG split)]
-
A.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
B.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
C.
isVesselFor
Indicates that one entity functions as a container or medium specifically used to hold, carry, or convey another entity.
-
D.
appliesToShips
chosen
Indicates that the specified condition, rule, or attribute is relevant to or affects ships.
-
E.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 29, 2026, 7:48 p.m.