Triple
T7374682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Dynamics Bath Iron Works |
E170093
|
entity |
| Predicate | hasShipbuildingWays |
P4334
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [General Dynamics Bath Iron Works, hasShipbuildingWays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipbuildingWays Context triple: [General Dynamics Bath Iron Works, hasShipbuildingWays, yes]
-
A.
shipbuildingActivity
Indicates the activity or process of constructing, assembling, or significantly modifying ships or large watercraft.
-
B.
shipyard
chosen
Indicates a relationship where a location functions as a facility for building, repairing, or maintaining ships.
-
C.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
D.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
E.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
- F. None of above.
Provenance (3 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a6643c81909d626c8b6a7a11fd |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.