Triple
T33754196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-6N |
E864926
|
entity |
| Predicate | notableWeaponIntegration |
P17728
|
FINISHED |
| Object | ALBM carried on centerline hardpoint |
—
|
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: ALBM carried on centerline hardpoint | Statement: [H-6N, notableWeaponIntegration, ALBM carried on centerline hardpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWeaponIntegration Context triple: [H-6N, notableWeaponIntegration, ALBM carried on centerline hardpoint]
-
A.
featuredWeapon
Indicates that a particular weapon is highlighted or prominently showcased in relation to an entity, such as a character, event, or context.
-
B.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
C.
weaponFeature
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
supportsWeapon
chosen
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.