Triple
T8739469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heavy cruiser Maya |
E207464
|
entity |
| Predicate | enhancedArmament |
P84582
|
FINISHED |
| Object | anti-aircraft 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: anti-aircraft guns | Statement: [heavy cruiser Maya, enhancedArmament, anti-aircraft guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enhancedArmament Context triple: [heavy cruiser Maya, enhancedArmament, anti-aircraft guns]
-
A.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
B.
greaterArmsFeature
Indicates that one entity possesses a more prominent or advanced arm-related feature than another entity.
-
C.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
rocketArmament
Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d486e34819094a6c6ec26c047cf |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:38 p.m.