Triple
T1581191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Washington (BB-47) |
E33764
|
entity |
| Predicate | plannedSecondaryBattery |
P21291
|
FINISHED |
| Object | 5-inch guns |
—
|
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: 5-inch guns | Statement: [USS Washington (BB-47), plannedSecondaryBattery, 5-inch guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSecondaryBattery Context triple: [USS Washington (BB-47), plannedSecondaryBattery, 5-inch guns]
-
A.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
B.
plannedMainBatteryConfiguration
chosen
Indicates the intended or designed primary weapon or main battery setup that was planned for an entity, typically before implementation or construction.
-
C.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
D.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
-
E.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.