Triple
T21509756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safavid Persian forces |
E530684
|
entity |
| Predicate | introducedFirearms |
P35807
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Safavid Persian forces, introducedFirearms, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFirearms Context triple: [Safavid Persian forces, introducedFirearms, 16th century]
-
A.
introducedWeaponSystem
chosen
Indicates that an entity caused a new weapon system to be brought into use or formally adopted.
-
B.
numberOfGuns
Indicates the quantity of guns associated with a given entity or situation.
-
C.
hasSmallCalibreGuns
Indicates that the subject is equipped with or possesses guns of relatively small calibre compared to standard or typical armaments.
-
D.
firearmActionType
Indicates the specific type or category of action performed with or by a firearm (such as firing, loading, carrying, or modifying).
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea84dfbc8190a23d9a7d6eb2c2b5 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.