Triple
T4720161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese battlecruiser Atago |
E104743
|
entity |
| Predicate | designedSecondaryArmament |
P6067
|
FINISHED |
| Object | 140 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: 140 mm guns | Statement: [Japanese battlecruiser Atago, designedSecondaryArmament, 140 mm guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedSecondaryArmament Context triple: [Japanese battlecruiser Atago, designedSecondaryArmament, 140 mm guns]
-
A.
secondaryArmament
chosen
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
B.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
numberOfMainBatteryGuns
Indicates the quantity of primary (main) battery guns that an entity, typically a warship or similar platform, is equipped with.
-
D.
rocketArmament
Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
-
E.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.