Triple
T9603201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Washington (BB-47) |
E231901
|
entity |
| Predicate | designedPower |
P10373
|
FINISHED |
| Object | 28000 shaft horsepower |
—
|
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: 28000 shaft horsepower | Statement: [USS Washington (BB-47), designedPower, 28000 shaft horsepower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPower Context triple: [USS Washington (BB-47), designedPower, 28000 shaft horsepower]
-
A.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
B.
designPowerOutput
chosen
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
C.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
D.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
E.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5af8f0819089408ed630afa812 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.