Triple
T16583206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | invasion of Italy (1494–1495) |
E402887
|
entity |
| Predicate | usesMilitaryTechnology |
P23907
|
FINISHED |
| Object | French 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: French artillery | Statement: [invasion of Italy (1494–1495), usesMilitaryTechnology, French artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMilitaryTechnology Context triple: [invasion of Italy (1494–1495), usesMilitaryTechnology, French artillery]
-
A.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
B.
militaryUse
chosen
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
C.
militaryInnovation
Indicates the introduction or development of new methods, technologies, or strategies within a military context.
-
D.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
E.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35999088c8190900497f18728bd0b |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.