Triple
T26305852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDG-1000 Zumwalt-class program |
E661679
|
entity |
| Predicate | shipClassDeveloped |
P160232
|
FINISHED |
| Object | Zumwalt-class destroyer |
—
|
NE NERFINISHED |
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: Zumwalt-class destroyer | Statement: [DDG-1000 Zumwalt-class program, shipClassDeveloped, Zumwalt-class destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipClassDeveloped Context triple: [DDG-1000 Zumwalt-class program, shipClassDeveloped, Zumwalt-class destroyer]
-
A.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
B.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
C.
navalClassGeneration
Indicates that one naval class belongs to a particular generational sequence or iteration relative to another naval class.
-
D.
plannedArmamentClass
Indicates that an entity is intended or designated to be equipped with a particular class or type of armament.
-
E.
shipDesigned
Indicates that one entity is responsible for designing or creating the design of a ship associated with another entity.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee2f18481908de53cc9872e96f4 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:18 p.m.