Triple
T36836069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmgewehr 44 |
E910273
|
entity |
| Predicate | hasIntendedEngagementRange |
P61967
|
FINISHED |
| Object | medium range combat |
—
|
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: medium range combat | Statement: [Sturmgewehr 44, hasIntendedEngagementRange, medium range combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedEngagementRange Context triple: [Sturmgewehr 44, hasIntendedEngagementRange, medium range combat]
-
A.
engagementRange
chosen
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
B.
hasSignalRange
Indicates that one entity possesses a communication or detection range within which it can send, receive, or detect signals relative to another entity or area.
-
C.
isInContactWith
Indicates that two entities are physically touching or directly connected so that contact between them is established.
-
D.
tieneAlcance
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
-
E.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.