Triple
T38090491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVE-73 |
E951098
|
entity |
| Predicate | associatedShipyard |
—
|
GENERATED |
| Object | Kaiser Shipyards |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedShipyard Context triple: [CVE-73, associatedShipyard, Kaiser Shipyards]
-
A.
hasShipyardIn
Indicates that an entity operates or possesses a shipyard located in a specified place.
-
B.
shipyardLocatedOn
Indicates that a shipyard is situated on or within the geographic area of a specified landmass, coastline, or body of water.
-
C.
shipyard
Indicates a relationship where a location functions as a facility for building, repairing, or maintaining ships.
-
D.
shipyardFormerName
Indicates that a shipyard previously operated under a different name, specifying what that former name was.
-
E.
hasShipyardType
Indicates the specific category or classification of shipyard associated with an entity.
- F. None of above. chosen
Provenance (1 batch)
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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.