Triple
T32979485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project 941 Akula |
E843756
|
entity |
| Predicate | locatedShipyard |
—
|
GENERATED |
| Object | Severodvinsk |
—
|
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: locatedShipyard Context triple: [Project 941 Akula, locatedShipyard, Severodvinsk]
-
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.
shipbuilderLocation
chosen
Indicates the location where a shipbuilder is based or operates.
-
D.
shipyardArea
Indicates the total physical area occupied or used by a shipyard for its operations.
-
E.
shipyard
Indicates a relationship where a location functions as a facility for building, repairing, or maintaining ships.
- F. None of above.
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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.