Triple
T37084955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casablanca-class escort carrier |
E918257
|
entity |
| Predicate | primaryShipyard |
P178062
|
FINISHED |
| Object | Kaiser Shipyards, Vancouver, Washington |
E919841
|
NE 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: Kaiser Shipyards, Vancouver, Washington | Statement: [Casablanca-class escort carrier, primaryShipyard, Kaiser Shipyards, Vancouver, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryShipyard Context triple: [Casablanca-class escort carrier, primaryShipyard, Kaiser Shipyards, Vancouver, Washington]
-
A.
hasShipyardIn
chosen
Indicates that an entity operates or possesses a shipyard located in a specified place.
-
B.
shipyard
Indicates a relationship where a location functions as a facility for building, repairing, or maintaining ships.
-
C.
shipyardLocatedOn
Indicates that a shipyard is situated on or within the geographic area of a specified landmass, coastline, or body of water.
-
D.
hasShipyardType
Indicates the specific category or classification of shipyard associated with an entity.
-
E.
shipyardArea
Indicates the total physical area occupied or used by a shipyard for its operations.
- F. None of above.
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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a0af49481908c7f858a0738311e |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.