Triple
T37398979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action at Beda Fomm |
E928937
|
entity |
| Predicate | hasPrimaryWeaponType |
P6066
|
FINISHED |
| Object | tanks |
—
|
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: tanks | Statement: [Action at Beda Fomm, hasPrimaryWeaponType, tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWeaponType Context triple: [Action at Beda Fomm, hasPrimaryWeaponType, tanks]
-
A.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
B.
primaryArmament
chosen
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
isOffensiveWeapon
Indicates that something qualifies as a weapon designed or used to cause harm or injury, typically in an aggressive or unlawful context.
-
D.
weaponryCarried
Indicates that one entity is carrying or equipped with a weapon or set of weapons in relation to another entity or context.
-
E.
isStartingWeaponFor
Indicates that a weapon is the initial or default weapon assigned to or used by an entity at the start of a game, scenario, or progression.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.