Triple
T6090790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwardian War |
E135757
|
entity |
| Predicate | hasMilitaryInnovation |
P20686
|
FINISHED |
| Object | tactical use of English longbowmen |
—
|
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: tactical use of English longbowmen | Statement: [Edwardian War, hasMilitaryInnovation, tactical use of English longbowmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryInnovation Context triple: [Edwardian War, hasMilitaryInnovation, tactical use of English longbowmen]
-
A.
militaryInnovation
chosen
Indicates the introduction or development of new methods, technologies, or strategies within a military context.
-
B.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
C.
hasNotableInnovation
Indicates that an entity is associated with a significant, distinguishing innovation or breakthrough.
-
D.
militaryProject
Indicates a project that is conducted, funded, or controlled by a military organization, typically for defense, security, or warfare-related purposes.
-
E.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057aa192081908619d3518d4efa7a |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.