Triple
T3718850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-Assyrian expansion |
E81591
|
entity |
| Predicate | usesMilitaryInnovation |
P6496
|
FINISHED |
| Object | iron weaponry |
—
|
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: iron weaponry | Statement: [Neo-Assyrian expansion, usesMilitaryInnovation, iron weaponry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMilitaryInnovation Context triple: [Neo-Assyrian expansion, usesMilitaryInnovation, iron weaponry]
-
A.
militaryInnovation
Indicates the introduction or development of new methods, technologies, or strategies within a military context.
-
B.
militaryTechnology
chosen
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
E.
militaryStrategy
Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca984844819087a2f6b20d2f19e7 |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.