Triple
T17682077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caio Duilio |
E440793
|
entity |
| Predicate | originalMainBattery |
P128556
|
FINISHED |
| Object | 13 × 305 mm 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: 13 × 305 mm guns | Statement: [Caio Duilio, originalMainBattery, 13 × 305 mm guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMainBattery Context triple: [Caio Duilio, originalMainBattery, 13 × 305 mm guns]
-
A.
plannedMainBatteryConfiguration
Indicates the intended or designed primary weapon or main battery setup that was planned for an entity, typically before implementation or construction.
-
B.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
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.
secondaryBatteryType
Indicates the type or category of a secondary (backup or auxiliary) battery associated with an entity.
-
E.
hasInternalBattery
Indicates that one entity possesses a built-in power source contained within itself, rather than relying solely on external power.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704514d481908aad4172fa930e6b |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.