Triple
T34919865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shangani Patrol |
E1007105
|
entity |
| Predicate | weaponUsedByBritish |
P29553
|
FINISHED |
| Object | rifles |
—
|
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: rifles | Statement: [Shangani Patrol, weaponUsedByBritish, rifles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponUsedByBritish Context triple: [Shangani Patrol, weaponUsedByBritish, rifles]
-
A.
weaponUsedIn
Indicates that a particular weapon is employed or involved in carrying out a specific event or action.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
D.
typicalOrdnance
chosen
Indicates that something is a standard or commonly used type of weaponry or munitions associated with a given entity or context.
-
E.
weaponOfInterest
Indicates that an entity is a weapon that is specifically relevant, notable, or targeted for attention within a given context or scenario.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.