Triple
T11674581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzungar–Qing Wars |
E277458
|
entity |
| Predicate | usedMilitaryTechnology |
P20686
|
FINISHED |
| Object | gunpowder weapons |
—
|
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: gunpowder weapons | Statement: [Dzungar–Qing Wars, usedMilitaryTechnology, gunpowder weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMilitaryTechnology Context triple: [Dzungar–Qing Wars, usedMilitaryTechnology, gunpowder weapons]
-
A.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
B.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
C.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
D.
militaryInnovation
chosen
Indicates the introduction or development of new methods, technologies, or strategies within a military context.
-
E.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a44504c48190b519765a83ff9c5e |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.