Triple
T31223701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Washington-class submarine |
E796081
|
entity |
| Predicate | hullDesignBasedOn |
P171042
|
FINISHED |
| Object | Skipjack-class submarine hull |
—
|
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: Skipjack-class submarine hull | Statement: [George Washington-class submarine, hullDesignBasedOn, Skipjack-class submarine hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullDesignBasedOn Context triple: [George Washington-class submarine, hullDesignBasedOn, Skipjack-class submarine hull]
-
A.
hullType
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.
hullWeight_kg
Indicates the weight of an object's hull measured in kilograms.
-
E.
sailDesign
Indicates a design relationship where one entity specifies or defines the shape, structure, or configuration of a sail used for propulsion.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4f35148190b58e80e79215092d |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 29, 2026, 9:10 p.m.