Triple
T24652115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wichita-class cruiser |
E610277
|
entity |
| Predicate | secondaryBatteryRole |
P157158
|
FINISHED |
| Object | dual-purpose 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: dual-purpose guns | Statement: [Wichita-class cruiser, secondaryBatteryRole, dual-purpose guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBatteryRole Context triple: [Wichita-class cruiser, secondaryBatteryRole, dual-purpose guns]
-
A.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
B.
secondaryBatteryType
Indicates the type or category of a secondary (backup or auxiliary) battery associated with an entity.
-
C.
secondaryBatteryLayout
Indicates how the secondary battery system is arranged or configured in relation to its associated components or structure.
-
D.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
E.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
- F. None of above. chosen
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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 2:34 a.m.