Triple
T32601816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Farragut (DLG-6) |
E833394
|
entity |
| Predicate | hullTypeAfter1975 |
P8584
|
FINISHED |
| Object | guided missile destroyer (DDG) |
—
|
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 (DDG) | Statement: [USS Farragut (DLG-6), hullTypeAfter1975, guided missile destroyer (DDG)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullTypeAfter1975 Context triple: [USS Farragut (DLG-6), hullTypeAfter1975, guided missile destroyer (DDG)]
-
A.
hullType
chosen
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
B.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
C.
hullWeight_lb
Indicates the weight of a hull measured in pounds.
-
D.
hullTypeConvertedFrom
Indicates that one hull type has been changed or transformed from another original hull type.
-
E.
hullDesignBasedOn
Indicates that the design of a vessel’s hull is derived from, influenced by, or modeled after another specified design or reference.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c69a1570819094a06cebc0c1c87d |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.