Triple
T2946391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Quincy (CA-39) |
E79511
|
entity |
| Predicate | armamentOther |
P6067
|
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: [USS Quincy (CA-39), armamentOther, anti-aircraft guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentOther Context triple: [USS Quincy (CA-39), armamentOther, anti-aircraft guns]
-
A.
armamentWartime
Indicates a relationship where an entity serves as a weapon or military equipment used by another entity specifically in a wartime context.
-
B.
secondaryArmament
chosen
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
C.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
D.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
-
E.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b3f86c819094526c2af611bfb5 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.