Triple
T9074580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Shipbuilding and Drydock Company |
E217452
|
entity |
| Predicate | navalVesselTypeBuilt |
P51721
|
FINISHED |
| Object | destroyer |
—
|
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: destroyer | Statement: [Federal Shipbuilding and Drydock Company, navalVesselTypeBuilt, destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalVesselTypeBuilt Context triple: [Federal Shipbuilding and Drydock Company, navalVesselTypeBuilt, destroyer]
-
A.
shipTypeProduced
chosen
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
B.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
C.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
D.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
E.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c4026c8190b553aedb9f4beabb |
completed | April 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.