Triple
T31543950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland-class cruiser |
E804821
|
entity |
| Predicate | secondaryBatteryConfiguration |
P143132
|
FINISHED |
| Object | six twin mounts |
—
|
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: six twin mounts | Statement: [Cleveland-class cruiser, secondaryBatteryConfiguration, six twin mounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBatteryConfiguration Context triple: [Cleveland-class cruiser, secondaryBatteryConfiguration, six twin mounts]
-
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
chosen
Indicates how the secondary battery system is arranged or configured in relation to its associated components or structure.
-
D.
secondaryBatteryRole
Indicates that an entity serves as a secondary or backup battery in relation to another primary power source or system.
-
E.
plannedMainBatteryConfiguration
Indicates the intended or designed primary weapon or main battery setup that was planned for an entity, typically before implementation or construction.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 30, 2026, 10:07 p.m.