Triple
T29059956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces of James Scott, 1st Duke of Monmouth |
E735499
|
entity |
| Predicate | primaryInfantryWeapon |
P7745
|
FINISHED |
| Object | musket |
—
|
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: musket | Statement: [Forces of James Scott, 1st Duke of Monmouth, primaryInfantryWeapon, musket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInfantryWeapon Context triple: [Forces of James Scott, 1st Duke of Monmouth, primaryInfantryWeapon, musket]
-
A.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
B.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
C.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
D.
weaponDepicted
Indicates that a weapon is visually represented or shown in association with an entity.
-
E.
limitedWeaponType
Indicates that the use or availability of a weapon is restricted to a specific type or set of types.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00b2b425a8819091ff65695e98c3af |
completed | May 10, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_6a00b06efa248190b2d16b4889185119 |
completed | May 10, 2026, 4:21 p.m. |
Created at: April 28, 2026, 10:14 a.m.