Triple
T5039974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish colonial wars in Morocco |
E113519
|
entity |
| Predicate | involvedMilitaryTechnology |
P6496
|
FINISHED |
| Object | artillery |
—
|
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: artillery | Statement: [Spanish colonial wars in Morocco, involvedMilitaryTechnology, artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedMilitaryTechnology Context triple: [Spanish colonial wars in Morocco, involvedMilitaryTechnology, artillery]
-
A.
militaryTechnology
chosen
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
B.
militaryInnovation
Indicates the introduction or development of new methods, technologies, or strategies within a military context.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
E.
militaryProject
Indicates a project that is conducted, funded, or controlled by a military organization, typically for defense, security, or warfare-related purposes.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73dd27fc8190817e53311ea3f706 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.